share_knowledge

SERVERFreedom Mcp SOURCEhttps://twuluxmoognlwtmaoqgo.supabase.co/functions/v1/freedom-mcp

Medium RISK CLASS

Category Write

Parameters 43 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-getfreedomos-freedom-mcp/share-knowledge.md

WHAT IT DOES

What share_knowledge does on Freedom Mcp

AI agents use share_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 share. Use trailing "/" for folders (e.g., "acme-deal/"). Use no trailing "/" for files (e.g., "acme-deal/term-sheet").
`companyId`	string	Yes	FreedomOS company id to act within (you must be a member). Required for company-scoped tools.
`permission`	string	—	Permission level: "read" (default) or "write".
`user_email`	string	Yes	Email of the FreedomOS user to share with.

Parameters from the server's own tool schema.

RISK

Why share_knowledge is rated Medium

This tool modifies system state by creating new access grants and updating metadata, making it a Write operation. It does not execute code/scripts (Execute), delete/destroy data (Destructive), move money (Financial), or merely query data (Read). Severity is medium because misuse could grant sensitive knowledge files to unintended users, though the approval gating mechanism mitigates some risk.

From the tool's definition Tool description states 'Creates a per-user access grant' and 'Front matter is auto-updated with audience metadata', indicating it modifies access control metadata and system state. The write-tier annotation confirms it creates new access records.

Risk signalsAccepts file system path (path)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs share_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 share_knowledge, this is the rule to start with:

share_knowledge Rate-limited

share_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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "share_knowledge": {
      "limits": [
        {
          "counter": "share_knowledge_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Freedom Mcp, apply this rule, and every share_knowledge call is checked against it from then on.

FAQ

Questions about share_knowledge

What does the share_knowledge tool do? +

Share a knowledge file or folder with a specific user. Creates a per-user access grant. The shared user's agent will also be able to read the files. Front matter is auto-updated with audience metadata so agents know the content is restricted. [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.

What parameters does share_knowledge accept? +

share_knowledge accepts 4 parameters: path, companyId, permission, user_email. Required: path, companyId, user_email. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on share_knowledge? +

Register the Freedom MCP server in PolicyLayer and add a rule for share_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.

What risk level is share_knowledge? +

share_knowledge is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit share_knowledge? +

Yes. Add a rate_limit block to the share_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.

How do I block share_knowledge completely? +

Set action: deny in the PolicyLayer policy for share_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.

What MCP server provides share_knowledge? +

share_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.

KEEP EXPLORING

More on Freedom, and thousands of servers like it.

This server

All 238 Freedom tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →