Removes renderings from an item by owners item ID.
AI agents call presentation-remove-rendering-by-id to permanently remove resources in SitecoreMCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Removing renderings from a Sitecore item modifies its presentation configuration in a way that is not easily reversible without a prior backup or version. This constitutes a destructive action as it permanently deletes layout/rendering associations from the item, potentially breaking page presentation across the site.
From the tool's definition 'Removes renderings from an item' — the word 'Removes' indicates an irreversible deletion of rendering configuration from a Sitecore item.
Attacks that exploit this kind of access
Removes renderings from an item by owners item ID. It is categorised as a Destructive tool in the SitecoreMCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Sitecore MCP server in PolicyLayer and add a rule for presentation-remove-rendering-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.
presentation-remove-rendering-by-id is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the presentation-remove-rendering-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 presentation-remove-rendering-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.
presentation-remove-rendering-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 →