The permission policy is blocking intended access without proving that its boundary is wrong.
Published applications need their delegated calls restored, and workspace isolation must remain intact.
Who you’d be doing this for
“My assistant opened the app this morning and every schedule lookup just spun.”
Shalini Agarwal · Founder of a scheduling startup
An entrepreneur running a published application whose staff can no longer retrieve appointment records.
What is at stake
Denied tool calls rose to 6.8% in two hours for newly published applications. You have to restore legitimate access without weakening the boundary between workspaces.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- access recovery vs workspace isolation
- fast rollback vs policy confidence
- alert quieting vs root-cause visibility
Why Replit
Agent-generated applications depend on delegated tool access that does not exceed the builder’s workspace permissions.
Written with these in mind
Not your kind of problem? 30 more at Replit, or browse every organization.
This is the setup. The work is inside.
Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.