policy_delete
AI agents call policy_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.
Policy deletion is irreversible and could catastrophically impact system access controls and security posture if invoked against the wrong policy. This falls squarely into the Destructive category.
From the tool's definition Tool name 'policy_delete' indicates permanent deletion of policies. The empty description prevents full assessment, but the verb 'delete' and the context of policy management strongly suggest irreversible removal of IAM or access policies.
Attacks that exploit this kind of access
policy_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.
Register the Amazon MQ MCP Server MCP server in PolicyLayer and add a rule for policy_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.
policy_delete 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 policy_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.
Set action: deny in the PolicyLayer policy for policy_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.
policy_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.