gateway_delete
AI agents call gateway_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.
The 'delete' operation combined with the empty description suggests a destructive action on broker gateway infrastructure. Without explicit recovery guarantees in the description, deletion of gateway resources in a message broker context represents an irreversible operation with high blast radius if triggered accidentally by an AI agent.
From the tool's definition Tool name 'gateway_delete' with empty description; 'delete' suffix indicates irreversible data removal. In the context of an Amazon MQ server for managing AMQ brokers, this likely deletes gateway configurations or broker infrastructure that cannot be undone.
Attacks that exploit this kind of access
gateway_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 gateway_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.
gateway_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 gateway_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 gateway_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.
gateway_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.