Critical Risk →

delete_app

delete_app

How to control delete_app ↓

What delete_app does on CloudWatch Application Signals MCP Server

AI agents call delete_app to permanently remove resources in CloudWatch Application Signals 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 needs a policy

The 'delete_app' tool performs irreversible deletion of an application, which cannot be undone. This falls into the Destructive category as it permanently removes data or resources. Given the CloudWatch Application Signals context (AWS monitoring/observability), this likely deletes application configurations, metrics, or monitoring setup.

From the tool's definition Tool name 'delete_app' indicates deletion of an application resource. No description provided, but the naming convention strongly suggests irreversible removal of data/infrastructure.

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

How to control delete_app

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

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

delete_app 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 CloudWatch Application Signals 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

What does the delete_app tool do? +

delete_app. It is categorised as a Destructive tool in the CloudWatch Application Signals 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? +

Register the CloudWatch Application Signals MCP Server 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 CloudWatch Application Signals MCP Server. 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 CloudWatch Application Signals MCP Server MCP server (awslabs.cloudwatch-applicationsignals-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every CloudWatch Application Signals MCP Server tool call.

Start from CloudWatch Application Signals 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.

805 CloudWatch Application Signals 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.