cms_update_collection
Patch a collection. When supplied,
This record as markdown: /tools/com-getmunin-munin/cms-update-collection.md
What cms_update_collection does on Munin
AI agents use cms_update_collection 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 cms_update_collection is rated Medium
The tool updates/patches a collection, which is a reversible Write operation. It does not delete data (Destructive), execute arbitrary code (Execute), move money (Financial), or merely read data (Read). The 'patch' semantic indicates partial modification rather than replacement, keeping it in Write rather than Destructive.
From the tool's definition Tool name is 'cms_update_collection' and description states 'Patch a collection', indicating modification of existing data in a reversible manner.
Attacks that exploit this kind of access
The rule that runs cms_update_collection 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_update_collection, this is the rule to start with:
cms_update_collection 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 cms_update_collection call is checked against it from then on.
Questions about cms_update_collection
Patch a collection. When supplied,. 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 cms_update_collection: 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_update_collection 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 cms_update_collection 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_update_collection. 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_update_collection 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