kb_update_document
Update a knowledge-base document. Pass
This record as markdown: /tools/com-getmunin-munin/kb-update-document.md
What kb_update_document does on Munin
AI agents use kb_update_document to create or update resources in Munin, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Munin environment.
Why kb_update_document is rated Medium
This tool creates or modifies data reversibly by updating documents in the knowledge base. It does not delete data (which would be Destructive), execute arbitrary code (Execute), or involve financial transactions (Financial).
From the tool's definition Tool name 'kb_update_document' and description 'Update a knowledge-base document' indicate modification of existing data within the knowledge base.
Attacks that exploit this kind of access
The rule that runs kb_update_document safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Munin, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For kb_update_document, this is the rule to start with:
kb_update_document 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 Munin, apply this rule, and every kb_update_document call is checked against it from then on.
Questions about kb_update_document
Update a knowledge-base document. Pass. It is categorised as a Write tool in the Munin MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Munin MCP server in PolicyLayer and add a rule for kb_update_document: 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 Munin. Nothing to install.
kb_update_document 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 kb_update_document 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 kb_update_document. 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.
kb_update_document is provided by the Munin MCP server (https://mcp.getmunin.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Munin, and thousands of servers like it.
This server
Across the catalogue