Returns all the clones for the specified item by its ID.
AI agents call common-get-item-clone-by-id to retrieve information from SitecoreMCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves data about item clones without creating, modifying, deleting, or executing any operations. It is a straightforward read operation that returns information based on an item ID parameter. The low severity reflects that retrieving metadata about clones poses minimal risk even if misused by an AI agent.
From the tool's definition Tool description states 'Returns all the clones for the specified item by its ID' — this is a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
Returns all the clones for the specified item by its ID. It is categorised as a Read tool in the SitecoreMCP MCP Server, which means it retrieves data without modifying state.
Register the Sitecore MCP server in PolicyLayer and add a rule for common-get-item-clone-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-get-item-clone-by-id is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the common-get-item-clone-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-get-item-clone-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-get-item-clone-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 →