Critical Risk →

delete

delete

How to control delete ↓

What delete does on Amazon MQ MCP Server

AI agents call delete to permanently remove resources in Amazon MQ 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 needs a policy

Despite the empty description, the tool name 'delete' in the context of a message broker management server indicates an irreversible destructive operation. This falls under Destructive rather than Execute because deletion operations cannot be undone. Severity is high rather than critical because impact is scoped to AMQ broker resources rather than broad infrastructure.

From the tool's definition Tool named 'delete' on Amazon MQ MCP Server for provisioning and managing AMQ brokers. The name 'delete' combined with the server's purpose of managing message brokers strongly suggests irreversible deletion of broker resources, configurations, or queue data.

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

How to control delete

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

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

delete 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 Amazon MQ 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

What does the delete tool do? +

delete. It is categorised as a Destructive tool in the Amazon MQ 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? +

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

What risk level is delete? +

delete 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? +

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

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

delete is provided by the Amazon MQ MCP Server MCP server (awslabs.amazon-mq-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 Amazon MQ MCP Server tool call.

Start from Amazon MQ 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 Amazon MQ 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.