delete_knowledge
Archive a knowledge file by slug (soft delete). The file is moved to _archived/ and can be restored later. Use when the user explicitly asks to remove a knowledge document. [write-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once ap...
This record as markdown: /tools/com-getfreedomos-freedom-mcp/delete-knowledge.md
What delete_knowledge does on Freedom Mcp
AI agents call delete_knowledge to permanently remove resources in Freedom Mcp, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
slug | string | Yes | The slug of the knowledge file to delete |
companyId | string | Yes | FreedomOS company id to act within (you must be a member). Required for company-scoped tools. |
Parameters from the server's own tool schema.
Why delete_knowledge is rated Critical
Moves file to archive; reversible but classified as destructive due to deletion semantics.
From the tool's definition soft delete... moved to _archived/ and can be restored later
Attacks that exploit this kind of access
The rule that runs delete_knowledge safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Freedom Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_knowledge, this is the rule to start with:
delete_knowledge 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 Freedom Mcp, apply this rule, and every delete_knowledge call is checked against it from then on.
Questions about delete_knowledge
Archive a knowledge file by slug (soft delete). The file is moved to _archived/ and can be restored later. Use when the user explicitly asks to remove a knowledge document. [write-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.]. It is categorised as a Destructive tool in the Freedom Mcp MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
delete_knowledge accepts 2 parameters: slug, companyId. Required: slug, companyId. The full parameter table on this page comes from the server's own tool schema.
Register the Freedom MCP server in PolicyLayer and add a rule for delete_knowledge: 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 Freedom Mcp. Nothing to install.
delete_knowledge 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 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. 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 is provided by the Freedom MCP server (https://twuluxmoognlwtmaoqgo.supabase.co/functions/v1/freedom-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Freedom, and thousands of servers like it.
Across the catalogue