context_batch_delete

THE RISK

Critical Risk

Why context_batch_delete needs a policy

This tool performs irreversible deletion of context data in bulk. Even though the data is internal to a session management system rather than user-facing files, the loss of conversation context, decisions, and work history cannot be undone. The atomic nature and pattern-matching capability increase the blast radius—an AI agent given loose parameters could delete substantially more context than intended.

From the tool's definition Delete multiple context items by keys or pattern in a single atomic operation. The verb 'delete' combined with 'multiple items' and 'atomic operation' indicates irreversible removal of data.

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

POLICY

How to control context_batch_delete

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

policy.json

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

context_batch_delete 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 MCP Memory Keeper — 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 MCP Memory Keeper tools

Execute context_delegate Delegate complex analysis tasks to specialized agents Execute context_watch Create and manage watchers for real-time context change monitoring Execute context_git_commit Create git commit with automatic context save Write context_session_start Start a new context session with optional project directory for git tracking Write context_cache_file Cache file content with hash for change detection Write context_integrate_tool Track events from other MCP tools Write context_reassign_channel Move context items between channels based on keys, patterns, or entire channel Write context_share Share a context item with other sessions for cross-session collaboration

All 40 MCP Memory Keeper 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 MCP Memory Keeper → 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 context_batch_delete

What does the context_batch_delete tool do? +

Delete multiple context items by keys or pattern in a single atomic operation. It is categorised as a Destructive tool in the MCP Memory Keeper 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 context_batch_delete? +

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

What risk level is context_batch_delete? +

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

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

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

context_batch_delete is provided by the MCP Memory Keeper MCP server (mkreyman/mcp-memory-keeper). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every MCP Memory Keeper tool call.

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

CHECK YOUR STACK →