delete_knowledge_document
Soft-delete a knowledge document. The agent loses access immediately, but the document can be restored with restore_knowledge_document.
This record as markdown: /tools/io-favcrm-favcrm/delete-knowledge-document.md
What delete_knowledge_document does on FavCRM
AI agents call delete_knowledge_document to permanently remove resources in FavCRM, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
documentId | string | Yes | Knowledge document ID |
Parameters from the server's own tool schema.
Why delete_knowledge_document is rated Critical
Although technically recoverable through restore_knowledge_document, this tool removes knowledge documents from immediate access, which qualifies as a destructive action. The agent loses immediate operational access to the document, and while recovery is possible, the primary effect is removal/deletion. In CRM contexts, losing access to knowledge documents could disrupt service operations.
From the tool's definition Tool name contains 'delete' and description states 'Soft-delete a knowledge document.' Even though soft-delete is reversible via restore_knowledge_document, the immediate loss of access and the use of 'delete' in the tool name indicates an irreversible action…
Attacks that exploit this kind of access
The rule that runs delete_knowledge_document safely
PolicyLayer is an MCP gateway: it sits between your AI agents and FavCRM, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_knowledge_document, this is the rule to start with:
delete_knowledge_document 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 FavCRM, apply this rule, and every delete_knowledge_document call is checked against it from then on.
Questions about delete_knowledge_document
Soft-delete a knowledge document. The agent loses access immediately, but the document can be restored with restore_knowledge_document. It is categorised as a Destructive tool in the FavCRM MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
delete_knowledge_document accepts 1 parameter: documentId. Required: documentId. The full parameter table on this page comes from the server's own tool schema.
Register the FavCRM MCP server in PolicyLayer and add a rule for delete_knowledge_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 FavCRM. Nothing to install.
delete_knowledge_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_knowledge_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_knowledge_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_knowledge_document is provided by the FavCRM MCP server (https://api.favcrm.io/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on FavCRM, and thousands of servers like it.
Across the catalogue