Critical Risk →

delete_agent_runtime

delete_agent_runtime

How to control delete_agent_runtime ↓

What delete_agent_runtime does on Amazon MQ MCP Server

AI agents call delete_agent_runtime 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_agent_runtime needs a policy

The 'delete_' prefix strongly suggests this tool removes or destroys data without recovery options. In the context of an Amazon MQ server managing brokers and agent runtimes, deleting a runtime would be an irreversible action that cannot be undone. Despite the empty description reducing confidence slightly, the naming convention is clear.

From the tool's definition Tool name 'delete_agent_runtime' contains 'delete', indicating irreversible data removal. Description is empty, limiting certainty.

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

How to control delete_agent_runtime

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_agent_runtime:

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

delete_agent_runtime 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_agent_runtime

What does the delete_agent_runtime tool do? +

delete_agent_runtime. 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_agent_runtime? +

Register the Amazon MQ MCP Server MCP server in PolicyLayer and add a rule for delete_agent_runtime: 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_agent_runtime? +

delete_agent_runtime 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_agent_runtime? +

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

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

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