This record as markdown: /tools/com-getmunin-munin/cms-create-entry.md
What cms_create_entry does on Munin
AI agents use cms_create_entry 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_create_entry is rated Medium
This tool creates new content/data entries in a CMS collection, which is a reversible write operation. It does not execute arbitrary code, delete data, move money, or retrieve data. The severity is medium because malicious use could spam or pollute content, but entries can typically be edited or deleted afterward. Confidence is high because the description clearly indicates content creation.
From the tool's definition Tool name is `cms_create_entry` and description states 'Create a new entry in a collection.' The verb 'Create' and explicit mention of creating entries indicates data modification.
Attacks that exploit this kind of access
The rule that runs cms_create_entry 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_create_entry, this is the rule to start with:
cms_create_entry 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_create_entry call is checked against it from then on.
Questions about cms_create_entry
Create a new entry in a collection. 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_create_entry: 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_create_entry 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_create_entry 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_create_entry. 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_create_entry 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