Critical Risk →

delete_app_cache

Delete a specific cache from an application.

How to control delete_app_cache ↓

What delete_app_cache does on Codemagic MCP Server

AI agents call delete_app_cache to permanently remove resources in Codemagic MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

Why delete_app_cache needs a policy

The delete_app_cache tool irreversibly removes cached data from a CI/CD application. Cache deletion cannot be undone—once deleted, the cache is gone and must be regenerated, causing build delays and potential loss of build artifacts. This makes it Destructive rather than merely Write.

From the tool's definition Tool name explicitly includes 'delete'; description states 'Delete a specific cache from an application' indicating irreversible removal of data.

Documented attack patterns abuse exactly the kind of access delete_app_cache gives an agent:

How to control delete_app_cache

PolicyLayer is an MCP gateway — it sits between your AI agents and Codemagic MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_app_cache:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_app_cache"
  ]
}

delete_app_cache disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register Codemagic MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about delete_app_cache

What does the delete_app_cache tool do? +

Delete a specific cache from an application. It is categorised as a Destructive tool in the Codemagic MCP Server 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_cache? +

Register the Codemagic MCP Server MCP server in PolicyLayer and add a rule for delete_app_cache: 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 Codemagic MCP Server. Nothing to install.

What risk level is delete_app_cache? +

delete_app_cache 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_cache? +

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

Set action: deny in the PolicyLayer policy for delete_app_cache. 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_cache? +

delete_app_cache is provided by the Codemagic MCP Server MCP server (stefanoamorelli/codemagic-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Codemagic MCP Server tool call.

Start from Codemagic MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

16 Codemagic MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.