Critical Risk →

clear_namespace

Delete all memories in a namespace.

Part of the Agent Memory server.

clear_namespace can permanently delete data in Agent Memory, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE AGENT MEMORY →

Free to start. No card required.

AI agents may call clear_namespace to permanently remove or destroy resources in Agent Memory. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. PolicyLayer blocks destructive tools by default and requires explicit human approval before enabling them.

Without a policy, an AI agent could call clear_namespace in a loop, permanently destroying resources in Agent Memory. There is no undo for destructive operations. PolicyLayer blocks this tool by default and only allows it when a human explicitly approves the action.

Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "clear_namespace"
  ]
}

See the full Agent Memory policy for all 5 tools.

Get this rule live on your own Agent Memory server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY AGENT MEMORY →

These attack patterns abuse exactly the kind of access clear_namespace gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so clear_namespace only ever does what you allow.

SECURE AGENT MEMORY →

Other destructive tools across the catalogue. The same approach applies to each: deny by default, or require human approval.

What does the clear_namespace tool do? +

Delete all memories in a namespace.. It is categorised as a Destructive tool in the Agent Memory MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on clear_namespace? +

Register the Agent Memory MCP server in PolicyLayer and add a rule for clear_namespace: 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 Agent Memory. Nothing to install.

What risk level is clear_namespace? +

clear_namespace is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit clear_namespace? +

Yes. Add a rate_limit block to the clear_namespace 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.

How do I block clear_namespace completely? +

Set action: deny in the PolicyLayer policy for clear_namespace. 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.

What MCP server provides clear_namespace? +

clear_namespace is provided by the Agent Memory MCP server (https://api.lazy-mac.com/agent-memory/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Agent Memory tool call.

Deterministic rules across all 5 Agent Memory tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.