// MCP TOOL REFERENCE

memory_purge

PERMANENTLY delete memories by id, tag, or substring match. This is destructive and cannot be undone! Use dryRun: true to preview first. Will request confirmation via elicitation if supported.

ServerCopilot Memory Store
CategoryDestructive

How to control memory_purge ↓

WHAT IT DOES

What memory_purge does on Copilot Memory Store

AI agents call memory_purge to permanently remove resources in Copilot Memory Store — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

THE RISK

Critical Risk

Why memory_purge needs a policy

This tool irreversibly deletes data without the ability to recover it. While not financial in nature, it represents the most severe non-financial category due to permanent data loss. The destructive impact is substantial if an AI agent misuses pattern matching to delete critical memories unintentionally.

From the tool's definition Tool description explicitly states: 'PERMANENTLY delete memories by id, tag, or substring match. This is destructive and cannot be undone!' The name 'memory_purge' and core functionality of permanent deletion directly indicate irreversible data removal.

Documented attack patterns abuse exactly the kind of access memory_purge gives an agent:

POLICY

How to control memory_purge

PolicyLayer is an MCP gateway — it sits between your AI agents and Copilot Memory Store, and nothing reaches the server without passing your rules. This is the rule we recommend for memory_purge:

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "memory_purge"
  ]
}

memory_purge disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

Create a free account and register Copilot Memory Store — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Copilot Memory Store tools

Destructive memory_delete Soft-delete a memory by ID (tombstone). The memory is marked as deleted but remains in sto Write memory_write Add, save, store, or remember information to the project memory. Use this when the user wa Read inject_context Inject relevant project context for a coding task. Call this BEFORE starting work to retri Read memory_search Search, find, recall, or look up information from project memory. Use this when the user a Read memory_compress Create a compact Markdown context block from relevant memories, constrained to a character Read memory_export Export the complete memory store as raw JSON, including soft-deleted (tombstoned) items. U

All 7 Copilot Memory Store tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in Copilot Memory Store → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about memory_purge

What does the memory_purge tool do? +

PERMANENTLY delete memories by id, tag, or substring match. This is destructive and cannot be undone! Use dryRun: true to preview first. Will request confirmation via elicitation if supported. It is categorised as a Destructive tool in the Copilot Memory Store 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 memory_purge? +

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

What risk level is memory_purge? +

memory_purge 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 memory_purge? +

Yes. Add a rate_limit block to the memory_purge 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 memory_purge completely? +

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

memory_purge is provided by the Copilot Memory Store MCP server (timothywarner-org/copilot-memory-store). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Copilot Memory Store tool call.

Start from Copilot Memory Store, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →

Free to start. No card required.

7 Copilot Memory Store tools catalogued and risk-classified — across an index of 43,000+ MCP servers.