common-get-item-referrer-by-path

Gets items referring to a Sitecore item by its path, showing which items reference it.

Server SitecoreMCP ramseur/mcp-sitecore-server
Category Read
Risk class Low
Parameters 00 required

What common-get-item-referrer-by-path does on SitecoreMCP

AI agents call common-get-item-referrer-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.

Why common-get-item-referrer-by-path needs a policy

This tool retrieves referential metadata about items that point to a given Sitecore item. It performs a lookup query without side effects, altering no data, executing no code, and triggering no external operations. The blast radius of misuse is minimal: an agent could discover unwanted reference relationships but cannot modify, delete, or execute anything. This is a classic Read operation.

From the tool's definition Tool description states 'Gets items referring to a Sitecore item by its path, showing which items reference it' — a pure query/retrieval operation with no modification, deletion, or execution.

Questions about common-get-item-referrer-by-path

What does the common-get-item-referrer-by-path tool do? +

Gets items referring to a Sitecore item by its path, showing which items reference it. It is categorised as a Read tool in the SitecoreMCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on common-get-item-referrer-by-path? +

Register the Sitecore MCP server in PolicyLayer and add a rule for common-get-item-referrer-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.

What risk level is common-get-item-referrer-by-path? +

common-get-item-referrer-by-path is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit common-get-item-referrer-by-path? +

Yes. Add a rate_limit block to the common-get-item-referrer-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.

How do I block common-get-item-referrer-by-path completely? +

Set action: deny in the PolicyLayer policy for common-get-item-referrer-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.

What MCP server provides common-get-item-referrer-by-path? +

common-get-item-referrer-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.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.