delete_app

Delete an app from the registry. Default data:\

SERVEROpen Mcp Apps SOURCE@2nd1st/open-mcp-apps

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/2nd1st-open-mcp-apps/delete-app.md

WHAT IT DOES

What delete_app does on Open Mcp Apps

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

RISK

Why delete_app is rated Critical

Permanently removes app registry entries; cannot be undone without restoration.

From the tool's definition Delete an app from the registry. Irreversible data removal.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs delete_app safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Open Mcp Apps, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_app, this is the rule to start with:

delete_app Hidden

delete_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": [
    "delete_app"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about delete_app

What does the delete_app tool do? +

Delete an app from the registry. Default data:\. It is categorised as a Destructive tool in the Open Mcp Apps 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 delete_app? +

Register the Open Mcp Apps MCP server in PolicyLayer and add a rule for delete_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 Open Mcp Apps. Nothing to install.

What risk level is delete_app? +

delete_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 delete_app? +

Yes. Add a rate_limit block to the delete_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 delete_app completely? +

Set action: deny in the PolicyLayer policy for delete_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 delete_app? +

delete_app is provided by the Open Mcp Apps MCP server (@2nd1st/open-mcp-apps). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Open Mcp Apps, and thousands of servers like it.

This server

All 32 Open Mcp Apps tools → Critical-risk tools on this server →

Across the catalogue

sms_delete_message on Twilio SMS MCP Server →delete_snapshot on Why Did You Render →calendar_delete_event on Templonix Lite MCP Server →delete_addon_domain on cPanel MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →