unshare_knowledge
Revoke a user's access to a shared knowledge file or folder. [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.]
This record as markdown: /tools/com-getfreedomos-freedom-mcp/unshare-knowledge.md
What unshare_knowledge does on Freedom Mcp
AI agents use unshare_knowledge to create or update resources in Freedom Mcp, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Freedom Mcp environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
path | string | Yes | The file or folder path to unshare. Must match exactly what was originally shared. |
companyId | string | Yes | FreedomOS company id to act within (you must be a member). Required for company-scoped tools. |
user_email | string | Yes | Email of the user to revoke access from. |
Parameters from the server's own tool schema.
Why unshare_knowledge is rated Medium
Removes access permissions reversibly; does not delete data, just modifies sharing state.
From the tool's definition Revoke a user's access to a shared knowledge file or folder
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
The rule that runs unshare_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 unshare_knowledge, this is the rule to start with:
unshare_knowledge stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Freedom Mcp, apply this rule, and every unshare_knowledge call is checked against it from then on.
Questions about unshare_knowledge
Revoke a user's access to a shared knowledge file or folder. [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 Write tool in the Freedom Mcp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
unshare_knowledge accepts 3 parameters: path, companyId, user_email. Required: path, companyId, user_email. 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 unshare_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.
unshare_knowledge is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the unshare_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 unshare_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.
unshare_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.
This server
Across the catalogue