This tool deletes an entire namespace and all its memories. Use with caution as this action cannot be undone.
AI agents call deleteNamespace to permanently remove resources in MCP Memory — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes data without possibility of recovery. While it operates on user-scoped memory data rather than critical system resources, the irreversible nature of deletion and the warning against use establish it as Destructive rather than Write.
From the tool's definition The description explicitly states this tool 'deletes an entire namespace and all its memories' and warns 'this action cannot be undone.' The use of 'delete' and 'cannot be undone' directly indicates irreversible data destruction.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
This tool deletes an entire namespace and all its memories. Use with caution as this action cannot be undone. It is categorised as a Destructive tool in the MCP Memory MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the MCP Memory MCP server in PolicyLayer and add a rule for deleteNamespace: 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 MCP Memory. Nothing to install.
deleteNamespace 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 deleteNamespace 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 deleteNamespace. 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.
deleteNamespace is provided by the MCP Memory MCP server (redaphid/mcp-memory). 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 →