update_knowledge_section
Update a specific section of a knowledge file by its ## header. If the section exists, its content is replaced. If it doesn't exist, it's appended as a new section. Use this for surgical edits to guidelines or strategies without rewriting the entire file. [write-tier — first use may require a man...
This record as markdown: /tools/com-getfreedomos-freedom-mcp/update-knowledge-section.md
What update_knowledge_section does on Freedom Mcp
AI agents use update_knowledge_section 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 |
|---|---|---|---|
slug | string | Yes | The slug of the knowledge file to update |
companyId | string | Yes | FreedomOS company id to act within (you must be a member). Required for company-scoped tools. |
new_content | string | Yes | The new Markdown content for this section (replaces everything between this ## and the next ##). Use proper Markdown: blank lines between paragraphs, - for list |
section_header | string | Yes | The ## section header to find and replace (case-insensitive). If not found, appended as a new section. |
Parameters from the server's own tool schema.
Why update_knowledge_section is rated Medium
This tool modifies knowledge file content by updating or appending sections, which is a Write operation—reversible data modification. It is not Destructive because sections can be reverted and the entire file is not deleted. Severity is medium because misuse could corrupt business guidelines or strategies, affecting team operations, but the impact is limited to a single section and is recoverable.
From the tool's definition Tool description explicitly states: 'If the section exists, its content is replaced. If it doesn't exist, it's appended as a new section.' This is reversible modification of knowledge files. The write-tier notice confirms it creates or modifies data.
Attacks that exploit this kind of access
The rule that runs update_knowledge_section 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 update_knowledge_section, this is the rule to start with:
update_knowledge_section 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 update_knowledge_section call is checked against it from then on.
Questions about update_knowledge_section
Update a specific section of a knowledge file by its ## header. If the section exists, its content is replaced. If it doesn't exist, it's appended as a new section. Use this for surgical edits to guidelines or strategies without rewriting the entire file. [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.
update_knowledge_section accepts 4 parameters: slug, companyId, new_content, section_header. Required: slug, companyId, new_content, section_header. 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 update_knowledge_section: 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.
update_knowledge_section 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 update_knowledge_section 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 update_knowledge_section. 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.
update_knowledge_section 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