memory_removeDocument
AI agents call memory_removeDocument 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 name implies removing/deleting a document from memory, which would be a destructive (irreversible deletion) action. However, since the description is empty, confidence is reduced. 'Remove' typically implies deletion rather than soft modification. Given sibling tool 'memory_clearMemory' also exists for a more sweeping operation, this tool likely deletes a specific document from memory storage.
From the tool's definition Tool name 'memory_removeDocument' suggests removal/deletion of a document from memory storage. Description is empty, providing no additional context.
Attacks that exploit this kind of access
memory_removeDocument. 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_removeDocument: 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_removeDocument 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_removeDocument 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_removeDocument. 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_removeDocument 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 →