delete-cache-cluster
AI agents call delete-cache-cluster 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.
The 'delete' operation removes infrastructure/data without the possibility of reversal. While the description is empty and provides no additional context, the tool name itself clearly denotes a destructive action that terminates a cache cluster, making it a Destructive category risk. Confidence is 0.85 rather than higher due to the empty description, but the naming convention is unambiguous.
From the tool's definition Tool name 'delete-cache-cluster' contains the verb 'delete', which explicitly indicates irreversible removal of a resource (a cache cluster).
Attacks that exploit this kind of access
delete-cache-cluster. 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.
Register the Amazon MQ MCP Server MCP server in PolicyLayer and add a rule for delete-cache-cluster: 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.
delete-cache-cluster is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete-cache-cluster 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.
Set action: deny in the PolicyLayer policy for delete-cache-cluster. 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.
delete-cache-cluster 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.