This record as markdown: /tools/deloc-mcp/enable-app.md
What enable_app does on Deloc
AI agents use enable_app to create or update resources in Deloc, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Deloc environment.
Why enable_app is rated Medium
The tool modifies application state (disabled → enabled) and has external consequences (app becomes served/live again), but the change is reversible (the app can be disabled again). This is Write-category behavior rather than Execute because it doesn't run arbitrary code or trigger deployment logic—it simply changes an app's enabled/disabled flag.
From the tool's definition Tool name 'enable_app' and description 'Re-enable a disabled app so it is served again' indicate a state-changing operation that activates a previously disabled application. This affects what is publicly served.
Attacks that exploit this kind of access
The rule that runs enable_app safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Deloc, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For enable_app, this is the rule to start with:
enable_app stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Deloc, apply this rule, and every enable_app call is checked against it from then on.
Questions about enable_app
Re-enable a disabled app so it is served again. It is categorised as a Write tool in the Deloc MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Deloc MCP server in PolicyLayer and add a rule for enable_app: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Deloc. Nothing to install.
enable_app is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the enable_app rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for enable_app. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
enable_app is provided by the Deloc MCP server (delocdev/deloc-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Deloc, and thousands of servers like it.
This server
Across the catalogue