memory_delete

THE RISK

Critical Risk

Why memory_delete needs a policy

This tool irreversibly deletes data from shared memory used by multiple AI agents for coordination. Deletion cannot be undone, making it destructive. The severity is high because in a multi-agent orchestration system, shared memory is critical infrastructure; malicious or accidental deletion could disrupt agent coordination, cause data loss, and break task workflows across multiple agents and tools.

From the tool's definition Tool name is 'memory_delete' and description states 'Delete a value from shared memory.' The verb 'delete' indicates irreversible removal of data.

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

POLICY

How to control memory_delete

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

policy.json

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

memory_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 Agent Orchestration — 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 Agent Orchestration tools

Destructive agent_unregister Unregister this agent and release all held locks. Call at the end of your session. Execute bootstrap Initialize agent session: register (if needed), get current focus, pending tasks, and rece Execute cursor_recover_task Recover a failed or stale delegated Cursor task by relaunching it with the latest shared c Execute lock_acquire Acquire a lock on a resource to prevent concurrent access. Write claim_todo FOR SUB-AGENTS: Register yourself AND claim a specific task in one call. Use this when you Write cursor_delegate_task Delegate a task to Cursor CLI and store session metadata for later resume/sync. Write cursor_sync_task Refresh a delegated Cursor task, sync the latest provider status, and persist knowledge ba Write research_ready Mark research as complete for a task. Validates that all required research items are docum

All 35 Agent Orchestration 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 Agent Orchestration → 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_delete

What does the memory_delete tool do? +

Delete a value from shared memory. It is categorised as a Destructive tool in the Agent Orchestration 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_delete? +

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

What risk level is memory_delete? +

memory_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 memory_delete? +

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

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

memory_delete is provided by the Agent Orchestration MCP server (madebyaris/agent-orchestration). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Agent Orchestration tool call.

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

CHECK YOUR STACK →