Delete a rule by its id. Soft-deletes (archives) unless hard=True.
AI agents call memory_delete_rule to permanently remove resources in Claude Memory MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool deletes rules that enforce constraints within the memory system. Even soft-deletion (archival) removes active rules; hard deletion is irreversible. Unauthorized deletion of rules could disable critical safeguards or constraints. While the blast radius is narrower than data deletion, the irreversible nature and potential to compromise system governance classifies this as Destructive rather than Write.
From the tool's definition Tool performs 'Delete a rule by its id' with option to hard-delete (archive by default, but permanent deletion possible). The description explicitly mentions deletion capability, and hard=True enables irreversible removal.
Attacks that exploit this kind of access
Delete a rule by its id. Soft-deletes (archives) unless hard=True. It is categorised as a Destructive tool in the Claude Memory MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Claude Memory MCP server in PolicyLayer and add a rule for memory_delete_rule: 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 Claude Memory MCP. Nothing to install.
memory_delete_rule 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 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_rule. 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_rule is provided by the Claude Memory MCP server (navid-kianfar/claude-memory-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 →