gateway_delete
AI agents call gateway_delete to permanently remove resources in AWS IoT SiteWise MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool performs a delete operation on an AWS IoT SiteWise gateway, which is an irreversible action that cannot be undone. This falls into the Destructive category (more severe than Write or Execute) due to the permanent nature of the operation. Severity is high because deletion of IoT infrastructure could disrupt monitoring and data collection.
From the tool's definition Tool name 'gateway_delete' indicates deletion of a gateway resource. The 'delete' verb signifies irreversible removal of data or infrastructure. No description provided, but the naming convention is unambiguous.
Attacks that exploit this kind of access
gateway_delete. It is categorised as a Destructive tool in the AWS IoT SiteWise MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the AWS IoT SiteWise 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 AWS IoT SiteWise 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 AWS IoT SiteWise MCP Server MCP server (awslabs.aws-iot-sitewise-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.