gateway_target_delete
AI agents call gateway_target_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.
Although the description is empty (lowering confidence slightly), the 'delete' verb in the tool name is a strong signal of destructive intent. In the context of Amazon MQ broker provisioning and management, deleting a gateway target would remove critical network infrastructure with potential service disruption. This falls into Destructive rather than Write because deletion is irreversible.
From the tool's definition Tool name is 'gateway_target_delete' with an empty description. The 'delete' operation in a broker management context (Amazon MQ) indicates irreversible removal of gateway target configuration or infrastructure.
Attacks that exploit this kind of access
gateway_target_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_target_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_target_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_target_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_target_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_target_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.