memory_clearMemory
AI agents call memory_clearMemory to permanently remove resources in Chain Debugger MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool appears to clear or delete memory contents, which is an irreversible operation. In the context of a blockchain debugging server where memory likely stores important transaction analysis, alerts, or simulation data, clearing memory cannot be undone and represents data loss. This qualifies as Destructive rather than Write due to the irreversible nature of clearing/deletion operations.
From the tool's definition Tool name 'memory_clearMemory' indicates deletion/clearing of stored memory data. No description provided, but naming convention strongly suggests irreversible removal of data.
Attacks that exploit this kind of access
memory_clearMemory. It is categorised as a Destructive tool in the Chain Debugger MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Chain Debugger MCP Server MCP server in PolicyLayer and add a rule for memory_clearMemory: 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 Chain Debugger MCP Server. Nothing to install.
memory_clearMemory 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 memory_clearMemory 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 memory_clearMemory. 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.
memory_clearMemory is provided by the Chain Debugger MCP Server MCP server (optimusopus/chain-debugger-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →