delete_memory

Delete a memory entry

SERVERNcp SOURCE@portel/ncp

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-portel-dev-ncp/delete-memory.md

WHAT IT DOES

What delete_memory does on Ncp

AI agents call delete_memory to permanently remove resources in Ncp, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why delete_memory is rated Critical

Deletion operations cannot be undone and result in permanent data loss. While 'memory' may refer to cached or session state (not necessarily critical data), the irreversible nature of deletion and the lack of specification about what 'memory' contains justifies the Destructive category and high severity.

From the tool's definition Tool name is 'delete_memory' and description states 'Delete a memory entry' — the verb 'delete' indicates irreversible removal of data.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs delete_memory safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Ncp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_memory, this is the rule to start with:

delete_memory Hidden

delete_memory is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

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

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Ncp, apply this rule, and every delete_memory call is checked against it from then on.

FAQ

Questions about delete_memory

What does the delete_memory tool do? +

Delete a memory entry. It is categorised as a Destructive tool in the Ncp 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 delete_memory? +

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

What risk level is delete_memory? +

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

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

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

delete_memory is provided by the Ncp MCP server (@portel/ncp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Ncp, and thousands of servers like it.

This server

All 275 Ncp tools → Critical-risk tools on this server →

Across the catalogue

delete_memory on Cognio →sms_delete_message on Twilio SMS MCP Server →delete_snapshot on Why Did You Render →calendar_delete_event on Templonix Lite MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Blast radius →Tool call approval →