Sets the item template by the item
AI agents use common-set-item-template-by-id to create or update resources in SitecoreMCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your SitecoreMCP environment.
This tool modifies an existing item's template attribute, which is a reversible change to Sitecore content structure. While not destructive (the change can be undone), it alters data state and could have significant blast radius if an AI agent mistakenly reassigns templates to critical items, affecting content rendering and behavior.
From the tool's definition Tool name contains 'set-item-template' and description states 'Sets the item template by the item', indicating modification of an item's template property in Sitecore.
Attacks that exploit this kind of access
Sets the item template by the item. It is categorised as a Write tool in the SitecoreMCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Sitecore MCP server in PolicyLayer and add a rule for common-set-item-template-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-set-item-template-by-id 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 common-set-item-template-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-set-item-template-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-set-item-template-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 →