DeleteAHOBatch
AI agents call DeleteAHOBatch to permanently remove resources in Amazon ElastiCache Memcached MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Delete operations are irreversible by definition. Even without a full description, the explicit 'Delete' verb in the tool name indicates this tool removes data without undo capability. In the context of ElastiCache, deleting batches could impact cached data or read set configurations.
From the tool's definition Tool name 'DeleteAHOBatch' uses the verb 'Delete', which indicates irreversible removal of data. The 'AHOBatch' suffix suggests it operates on batches within Amazon ElastiCache Memcached's Active-Healthy-Only (AHO) read set functionality.
Attacks that exploit this kind of access
DeleteAHOBatch. It is categorised as a Destructive tool in the Amazon ElastiCache Memcached MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Amazon ElastiCache Memcached 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 Amazon ElastiCache Memcached 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 Amazon ElastiCache Memcached MCP Server MCP server (awslabs.memcached-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.