Delete a memory by ID (requires confirmation)
AI agents call delete_memory to permanently remove resources in Agentic Tools MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deletion is an irreversible operation that removes data and cannot be undone. This fits the Destructive category definition: 'irreversibly deletes or overwrites data, or actions that cannot be undone (delete, drop, purge, force-push).' The confirmation requirement provides some mitigation but does not change the fundamental destructive nature.
From the tool's definition Tool name is 'delete_memory' and description states 'Delete a memory by ID'. The verb 'delete' indicates irreversible removal of data. Although 'requires confirmation' adds a safeguard, the core operation is destructive.
Documented attack patterns abuse exactly the kind of access delete_memory gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Agentic Tools MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_memory:
{
"version": "1",
"default": "deny",
"hide": [
"delete_memory"
]
}delete_memory disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Delete a memory by ID (requires confirmation). It is categorised as a Destructive tool in the Agentic Tools MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Agentic Tools MCP Server MCP server in PolicyLayer and add a rule for delete_memory: 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 Agentic Tools MCP Server. Nothing to install.
delete_memory 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_memory 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_memory. 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_memory is provided by the Agentic Tools MCP Server MCP server (pimzino/agentic-tools-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 29 Agentic Tools MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
29 Agentic Tools MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.