cms_schedule_publish
Schedule an entry to flip to published at a future ISO 8601 datetime. The schedule worker drains due rows every minute. Content is unchanged, so the entry comes back as a summary unless
This record as markdown: /tools/com-getmunin-munin/cms-schedule-publish.md
What cms_schedule_publish does on Munin
AI agents use cms_schedule_publish 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_schedule_publish is rated Medium
Schedules content publication reversibly; modifies state without deletion or irreversible changes.
From the tool's definition Schedule an entry to flip to published at a future datetime.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs cms_schedule_publish 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_schedule_publish, this is the rule to start with:
cms_schedule_publish 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_schedule_publish call is checked against it from then on.
Questions about cms_schedule_publish
Schedule an entry to flip to published at a future ISO 8601 datetime. The schedule worker drains due rows every minute. Content is unchanged, so the entry comes back as a summary unless. 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_schedule_publish: 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_schedule_publish 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_schedule_publish 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_schedule_publish. 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_schedule_publish 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