cms_list_versions
List all prior versions of an entry, newest first.
This record as markdown: /tools/com-getmunin-munin/cms-list-versions.md
What cms_list_versions does on Munin
AI agents call cms_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.
Why cms_list_versions is rated Low
This tool queries and retrieves version history metadata. It performs a read-only operation with no side effects on the data. The blast radius of misuse is minimal—an agent could access historical versions of content, but cannot modify, delete, or execute operations. This fits the Read category definition: 'retrieves or queries data; no side effects'.
From the tool's definition 'List all prior versions of an entry' - retrieves historical data without modification, creation, or deletion of records.
Attacks that exploit this kind of access
The rule that runs cms_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 cms_list_versions, this is the rule to start with:
cms_list_versions is read-only, so it stays allowed. 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 cms_list_versions call is checked against it from then on.
Questions about cms_list_versions
List all prior versions of an entry, newest first. It is categorised as a Read tool in the Munin MCP Server, which means it retrieves data without modifying state.
Register the Munin MCP server in PolicyLayer and add a rule for cms_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.
cms_list_versions is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the cms_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.
Set action: deny in the PolicyLayer policy for cms_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.
cms_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.
More on Munin, and thousands of servers like it.
This server
Across the catalogue