delete_knowledge_category
Delete a knowledge base category. Documents in the category will become uncategorized (not deleted).
This record as markdown: /tools/flowdot-llc-mcp-server/delete-knowledge-category.md
What delete_knowledge_category does on FlowDot MCP Server
AI agents call delete_knowledge_category 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_category is rated Critical
This tool performs an irreversible deletion of a knowledge base category. Although documents are not permanently removed, the category itself and its associated organizational structure are destroyed and cannot be undone. This qualifies as Destructive rather than Write because deletion is not a reversible modification.
From the tool's definition Tool name contains 'delete' and description states 'Delete a knowledge base category'; the action is irreversible—once deleted, the category structure is removed and cannot be recovered, even though documents within are preserved.
Attacks that exploit this kind of access
The rule that runs delete_knowledge_category safely
PolicyLayer is an MCP gateway: it sits between your AI agents and FlowDot MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_knowledge_category, this is the rule to start with:
delete_knowledge_category 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 FlowDot MCP Server, apply this rule, and every delete_knowledge_category call is checked against it from then on.
Questions about delete_knowledge_category
Delete a knowledge base category. Documents in the category will become uncategorized (not deleted). 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.
Register the FlowDot MCP Server MCP server in PolicyLayer and add a rule for delete_knowledge_category: 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.
delete_knowledge_category 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_category 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_category. 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_category 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.
Across the catalogue