cms_update_entry

Update an entry. Pass

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

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/com-getmunin-munin/cms-update-entry.md

WHAT IT DOES

What cms_update_entry does on Munin

AI agents use cms_update_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.

RISK

Why cms_update_entry is rated Medium

This tool modifies existing CMS entries, which is a reversible operation. It does not delete data (would be Destructive), does not execute arbitrary code (would be Execute), and does not involve financial transactions (would be Financial).

From the tool's definition Tool name 'cms_update_entry' with description 'Update an entry' indicates modification of content management system data. The verb 'update' is explicitly Write-category (creates or modifies data reversibly).

Attacks that exploit this kind of access

RECOMMENDED RULE

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

cms_update_entry Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "cms_update_entry": {
      "limits": [
        {
          "counter": "cms_update_entry_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about cms_update_entry

What does the cms_update_entry tool do? +

Update an entry. Pass. 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.

How do I enforce a policy on cms_update_entry? +

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

What risk level is cms_update_entry? +

cms_update_entry is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit cms_update_entry? +

Yes. Add a rate_limit block to the cms_update_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.

How do I block cms_update_entry completely? +

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

What MCP server provides cms_update_entry? +

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

KEEP EXPLORING

More on Munin, and thousands of servers like it.

This server

All 242 Munin tools →

Across the catalogue

aroflo_create_or_update_record on AroFlo MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →