memory_delete
AI agents call memory_delete 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.
The tool name explicitly contains 'delete', which maps to the Destructive category. While the description is empty (lowering confidence slightly), the combination of the tool name and the ElastiCache Memcached server context makes it clear this performs irreversible data deletion. An AI agent misusing this could purge critical cached data, causing data loss and application failures.
From the tool's definition Tool name 'memory_delete' with ElastiCache Memcached context indicates deletion of cache entries or memory data. Memcached operations to delete data are irreversible; once purged from the in-memory cache, data cannot be recovered without external persistence.
Attacks that exploit this kind of access
memory_delete. 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 memory_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 ElastiCache Memcached MCP Server. Nothing to install.
memory_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 memory_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 memory_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.
memory_delete 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.