DeleteAHOBatch
AI agents call DeleteAHOBatch 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 name explicitly indicates a delete operation on batch data (AHO = likely an AWS IoT SiteWise entity type). Delete operations are irreversible and cannot be undone, placing this in the Destructive category. The ability to delete multiple items in a batch makes this critical severity, as a single misuse could remove substantial amounts of data without recovery.
From the tool's definition Tool name 'DeleteAHOBatch' contains the verb 'Delete', which indicates irreversible removal of data. The 'Batch' suffix suggests it operates on multiple records at once, amplifying the blast radius.
Attacks that exploit this kind of access
DeleteAHOBatch. 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 DeleteAHOBatch: 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.
DeleteAHOBatch 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 DeleteAHOBatch 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 DeleteAHOBatch. 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.
DeleteAHOBatch 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.