Switches an existing rendering specified by path with an alternate one for the item specified by path.
AI agents use presentation-switch-rendering-by-path 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.
The tool modifies presentation configurations for items in Sitecore, which is a reversible change (renderings can be switched back or replaced). This qualifies as Write rather than Destructive since the operation doesn't irreversibly delete data.
From the tool's definition Switches an existing rendering specified by path with an alternate one for the item specified by path. This modifies presentation layer components of content items, changing their rendering output.
Attacks that exploit this kind of access
Switches an existing rendering specified by path with an alternate one for the item specified by path. 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 presentation-switch-rendering-by-path: 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.
presentation-switch-rendering-by-path 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 presentation-switch-rendering-by-path 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 presentation-switch-rendering-by-path. 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.
presentation-switch-rendering-by-path 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 →