Delete document (cascades memory associations). WHEN: Removing obsolete, incorrect, or no-longer-relevant documents. BEHAVIOR: Permanently deletes document and removes memory associations. Memories themselves are preserved. Cannot be undone. NOT-USE: For temporary hiding (no undo available), or u...
AI agents call delete_document to permanently remove resources in Forgetful — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly deletes data (documents and their memory associations) with no undo capability. It matches the Destructive category definition: 'irreversibly deletes or overwrites data, or actions that cannot be undone.' The description explicitly states 'Cannot be undone' and warns against use for 'temporary hiding (no undo available).' While the blast radius is limited to a knowledge base document rather…
From the tool's definition Permanently deletes document and removes memory associations. Cannot be undone.
Documented attack patterns abuse exactly the kind of access delete_document gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Forgetful, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_document:
{
"version": "1",
"default": "deny",
"hide": [
"delete_document"
]
}delete_document disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Delete document (cascades memory associations). WHEN: Removing obsolete, incorrect, or no-longer-relevant documents. BEHAVIOR: Permanently deletes document and removes memory associations. Memories themselves are preserved. Cannot be undone. NOT-USE: For temporary hiding (no undo available), or updating (use update_document). Args: document_id: Document ID to delete ctx: Context (automatically injected) Returns: Success confirmation with deleted document ID Raises: ToolError if document not found. It is categorised as a Destructive tool in the Forgetful MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Forgetful MCP server in PolicyLayer and add a rule for delete_document: 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 Forgetful. Nothing to install.
delete_document 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 delete_document 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 delete_document. 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.
delete_document is provided by the Forgetful MCP server (scottrbk/forgetful). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 59 Forgetful tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
59 Forgetful tools catalogued and risk-classified — across an index of 42,500+ MCP servers.