disable_app

Take a published app offline

SERVERDeloc SOURCEdelocdev/deloc-mcp

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/deloc-mcp/disable-app.md

WHAT IT DOES

What disable_app does on Deloc

AI agents call disable_app to permanently remove resources in Deloc, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why disable_app is rated Critical

Taking a published app offline is effectively irreversible in its immediate impact (the app becomes unavailable to users the moment it's disabled). While it may technically be re-enabled, the act of disabling is a destructive operational action with high blast radius — it can break live services, disrupt end users, and cause downtime. This warrants the Destructive category at high severity.

From the tool's definition "Take a published app offline" — disabling a live app is a hard operational change that removes public availability

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs disable_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 disable_app, this is the rule to start with:

disable_app Hidden

disable_app is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "disable_app"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Deloc, apply this rule, and every disable_app call is checked against it from then on.

FAQ

Questions about disable_app

What does the disable_app tool do? +

Take a published app offline. It is categorised as a Destructive tool in the Deloc MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on disable_app? +

Register the Deloc MCP server in PolicyLayer and add a rule for disable_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.

What risk level is disable_app? +

disable_app is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit disable_app? +

Yes. Add a rate_limit block to the disable_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.

How do I block disable_app completely? +

Set action: deny in the PolicyLayer policy for disable_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.

What MCP server provides disable_app? +

disable_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.

KEEP EXPLORING

More on Deloc, and thousands of servers like it.

This server

All 45 Deloc tools → Critical-risk tools on this server →

Across the catalogue

unregister_passenger_app on cPanel MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →