Gets item fields as either names or fields or template fields by its path.
AI agents call common-get-item-field-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 performs a read-only query operation that retrieves item field information from Sitecore by path. It has no side effects, does not modify data, execute commands, or delete content. The low severity reflects the minimal blast radius if misused—an attacker would only gain access to field data visibility, not data modification or system compromise.
From the tool's definition Tool name contains 'get' and description states 'Gets item fields'; the operation retrieves data by path with no modification, creation, deletion, or execution capability.
Attacks that exploit this kind of access
Gets item fields as either names or fields or template fields 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 common-get-item-field-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.
common-get-item-field-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 common-get-item-field-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 common-get-item-field-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.
common-get-item-field-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 →