delete_resource
AI agents call delete_resource 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 name 'delete_resource' clearly indicates deletion functionality. In AWS IoT SiteWise context, this would irreversibly remove data or infrastructure configurations. Although the description is empty (lowering confidence slightly), the semantic meaning of 'delete' in resource management contexts is unambiguous—it performs an operation that cannot be undone.
From the tool's definition Tool name is 'delete_resource' which indicates irreversible deletion of resources in AWS IoT SiteWise. The empty description prevents full certainty, but the verb 'delete' is unambiguous.
Attacks that exploit this kind of access
delete_resource. 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 delete_resource: 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.
delete_resource 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_resource 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_resource. 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_resource 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.