kb_restore_version
Roll a document back to an earlier version. Creates a new current version with that historical content. Returns the full restored document, or a summary with
This record as markdown: /tools/com-getmunin-munin/kb-restore-version.md
What kb_restore_version does on Munin
AI agents use kb_restore_version 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_restore_version is rated Medium
Modifies document content by restoring historical version as new current state, reversible by further restoration.
From the tool's definition Roll document back to earlier version, creates new current version
Attacks that exploit this kind of access
The rule that runs kb_restore_version 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_restore_version, this is the rule to start with:
kb_restore_version 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_restore_version call is checked against it from then on.
Questions about kb_restore_version
Roll a document back to an earlier version. Creates a new current version with that historical content. Returns the full restored document, or a summary with. 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_restore_version: 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_restore_version 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_restore_version 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_restore_version. 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_restore_version 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