delete_knowledge_document

Permanently delete a document from your knowledge base. This removes the file and all associated chunks/embeddings.

SERVERFlowDot MCP Server SOURCEflowdot-llc/mcp-server
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/flowdot-llc-mcp-server/delete-knowledge-document.md

What delete_knowledge_document does on FlowDot MCP Server

AI agents call delete_knowledge_document to permanently remove resources in FlowDot MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why delete_knowledge_document is rated Critical

This tool performs permanent, irreversible deletion of data from a knowledge base. The description clearly indicates the action cannot be undone as it removes the document file and all derivative embeddings. This meets the Destructive category definition of irreversibly deleting data.

From the tool's definition Tool description explicitly states "Permanently delete a document" which removes "the file and all associated chunks/embeddings" - irreversible deletion of data.

Questions about delete_knowledge_document

What does the delete_knowledge_document tool do? +

Permanently delete a document from your knowledge base. This removes the file and all associated chunks/embeddings. It is categorised as a Destructive tool in the FlowDot MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on delete_knowledge_document? +

Register the FlowDot MCP Server 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 FlowDot MCP Server. Nothing to install.

What risk level is delete_knowledge_document? +

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.

Can I rate-limit delete_knowledge_document? +

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.

How do I block delete_knowledge_document completely? +

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.

What MCP server provides delete_knowledge_document? +

delete_knowledge_document is provided by the FlowDot MCP Server MCP server (flowdot-llc/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on FlowDot MCP Server, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of FlowDot MCP Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.