Adds a rendering to presentation of an item specified by item ID.
AI agents use presentation-add-rendering-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 creates or modifies presentation renderings for a Sitecore item—a reversible change to content structure. It does not delete data (not Destructive), execute arbitrary code (not Execute), involve financial operations (not Financial), or retrieve data without side effects (not Read).
From the tool's definition Tool name contains 'add-rendering' and description states 'Adds a rendering to presentation of an item', indicating creation/modification of item presentation data.
Attacks that exploit this kind of access
Adds a rendering to presentation of an item specified by item ID. 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-add-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-add-rendering-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 presentation-add-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-add-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-add-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 →