kb_list_versions

List all prior versions of a knowledge-base document, newest first.

SERVERMunin SOURCEhttps://mcp.getmunin.com/mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/com-getmunin-munin/kb-list-versions.md

WHAT IT DOES

What kb_list_versions does on Munin

AI agents call kb_list_versions to retrieve information from Munin without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why kb_list_versions is rated Low

This tool only retrieves historical version metadata from a knowledge-base document. It does not create, modify, delete, or execute any operations—it simply queries and returns existing version information. The blast radius of misuse is minimal; an agent could only enumerate document histories, which is a read-only operation.

From the tool's definition Tool name 'kb_list_versions' and description 'List all prior versions of a knowledge-base document, newest first' indicate a retrieval/query operation with no side effects. The verb 'list' is explicitly retrieval-focused.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

kb_list_versions Allowed

kb_list_versions is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "kb_list_versions": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about kb_list_versions

What does the kb_list_versions tool do? +

List all prior versions of a knowledge-base document, newest first. It is categorised as a Read tool in the Munin MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on kb_list_versions? +

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

What risk level is kb_list_versions? +

kb_list_versions is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit kb_list_versions? +

Yes. Add a rate_limit block to the kb_list_versions 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 kb_list_versions completely? +

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

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

KEEP EXPLORING

More on Munin, and thousands of servers like it.

This server

All 242 Munin tools →

Across the catalogue

list_symbols on ACE-MCP →aiva_list_affiliates on AIVA MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →