Publishes a Sitecore item by its ID.
AI agents invoke common-publish-item-by-id to trigger actions in SitecoreMCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Publishing in Sitecore is an external operation that pushes content from the authoring environment to live/delivery databases, affecting what end-users see in production. This is not a simple write (it triggers a workflow/deployment pipeline), and while it can sometimes be reversed by republishing older versions, the immediate effect on live sites makes it an Execute-level action with high blast radius if misused.
From the tool's definition 'Publishes a Sitecore item by its ID' — triggers an external publishing operation that propagates content to live/production environments
Attacks that exploit this kind of access
Publishes a Sitecore item by its ID. It is categorised as a Execute tool in the SitecoreMCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Sitecore MCP server in PolicyLayer and add a rule for common-publish-item-by-id: 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 SitecoreMCP. Nothing to install.
common-publish-item-by-id is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the common-publish-item-by-id 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 common-publish-item-by-id. 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.
common-publish-item-by-id is provided by the Sitecore MCP server (ramseur/mcp-sitecore-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →