Gets a Sitecore item by its URI.
AI agents call provider-get-item-by-uri 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 retrieves/queries a single item from a Sitecore CMS by its URI identifier. It performs a read-only lookup with no side effects, no data modification, no code execution, and no destructive action. The context of sibling tools (common-get-archive, common-get-cache, etc.) further confirms this is part of a read/retrieval family. Misuse would only expose existing data, hence low severity.
From the tool's definition Tool name 'provider-get-item-by-uri' and description 'Gets a Sitecore item by its URI' indicate a retrieval operation with the verb 'Gets' and no modification or deletion semantics.
Attacks that exploit this kind of access
Gets a Sitecore item by its URI. 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 provider-get-item-by-uri: 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.
provider-get-item-by-uri 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 provider-get-item-by-uri 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 provider-get-item-by-uri. 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.
provider-get-item-by-uri 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 →