This record as markdown: /tools/io-github-homenshum-nodebench/deleteagentmemory.md
What deleteAgentMemory does on Nodebench
AI agents call deleteAgentMemory to permanently remove resources in Nodebench, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why deleteAgentMemory is rated Critical
This tool performs irreversible deletion of agent memory entries. While the blast radius is scoped to memory storage (not system-wide data), deletion operations cannot be undone and represent a destructive action. The tool could be misused to erase important agent state, context, or decision history if an AI agent is given broad or incorrect keys to delete.
From the tool's definition Tool name 'deleteAgentMemory' with description 'Delete stored memory by key' uses the verb 'delete,' which indicates irreversible removal of data.
Attacks that exploit this kind of access
The rule that runs deleteAgentMemory safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Nodebench, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For deleteAgentMemory, this is the rule to start with:
deleteAgentMemory is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Nodebench, apply this rule, and every deleteAgentMemory call is checked against it from then on.
Questions about deleteAgentMemory
Delete stored memory by key. It is categorised as a Destructive tool in the Nodebench MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Nodebench MCP server in PolicyLayer and add a rule for deleteAgentMemory: 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 Nodebench. Nothing to install.
deleteAgentMemory is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the deleteAgentMemory 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.
Set action: deny in the PolicyLayer policy for deleteAgentMemory. 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.
deleteAgentMemory is provided by the Nodebench MCP server (nodebench-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Nodebench, and thousands of servers like it.
Across the catalogue