Delete a memory entry by its exact key.
AI agents call delete_memory to permanently remove resources in Jamot MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes data (a memory entry) without reversibility. While the blast radius is scoped to a single memory entry rather than bulk data, deletion operations are classified as Destructive per the taxonomy. The severity is high rather than critical because the impact is typically limited to a single memory record, not systemic data or financial harm.
From the tool's definition Tool name is 'delete_memory' with description 'Delete a memory entry by its exact key.' The verb 'Delete' combined with 'by its exact key' indicates irreversible removal of data.
Attacks that exploit this kind of access
Delete a memory entry by its exact key. It is categorised as a Destructive tool in the Jamot MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Jamot 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 Jamot MCP. 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 Jamot MCP server (jamot-pro/jamot-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →