Get a Sitecore item by its path.
AI agents call item-service-get-item-by-path 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 from Sitecore by path without side effects. It matches the Read category definition: retrieves or queries data with no side effects. The low severity reflects minimal blast radius—an AI agent misusing this would at worst retrieve sensitive data, but cannot modify, delete, or execute operations.
From the tool's definition Tool name contains 'get-item' and description explicitly states 'Get a Sitecore item by its path' — a straightforward retrieval operation with no modification, deletion, or execution semantics.
Attacks that exploit this kind of access
Get a Sitecore item by its path. 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 item-service-get-item-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.
item-service-get-item-by-path 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 item-service-get-item-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 item-service-get-item-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.
item-service-get-item-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 →