common-get-item-field-by-path

THE RISK

Low Risk

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

This tool queries and retrieves field information from Sitecore items without creating, modifying, deleting, or executing any operations. It is a straightforward data retrieval operation with no side effects, making it a Read category tool with low severity. The Sitecore context and sibling tools (which include write/add operations) confirm this is a read-only query function.

From the tool's definition Tool name and description indicate retrieval only: 'Gets item fields' with no modification, deletion, or execution verbs. Returns field data by path.

Documented attack patterns abuse exactly the kind of access common-get-item-field-by-path gives an agent:

POLICY

How to control common-get-item-field-by-path

PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Sitecore, and nothing reaches the server without passing your rules. This is the rule we recommend for common-get-item-field-by-path:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "common-get-item-field-by-path": {}
  }
}

common-get-item-field-by-path is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register Mcp Sitecore — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Mcp Sitecore tools

Destructive common-remove-archive-item Removes items permanently from the specified archive. Destructive common-remove-base-template-by-id Removes a base template from a template item by its ID. Destructive common-remove-item-version-by-id Removes a version of a Sitecore item by ID. Destructive common-remove-item-version-by-path Removes a version of a Sitecore item by path. Destructive indexing-remove-search-index-item-by-id Removes the item with the specified ID from the search index. Supports wildcard filtering Destructive indexing-remove-search-index-item-by-path Removes the item with the specified path from the search index. Supports wildcard filterin Destructive item-service-delete-item Delete a Sitecore item by its ID. Destructive presentation-remove-placeholder-setting-by-id Removes placeholder setting from the item specified by ID.

All 149 Mcp Sitecore tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

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

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

Gets item fields as either names or fields or template fields by its path. It is categorised as a Read tool in the Mcp Sitecore MCP Server, which means it retrieves data without modifying state.

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

Register the Mcp 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 Mcp Sitecore. Nothing to install.

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

common-get-item-field-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-field-by-path? +

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.

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

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.

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

common-get-item-field-by-path is provided by the Mcp Sitecore MCP server (@antonytm/mcp-sitecore-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Mcp Sitecore tool call.

Start from Mcp Sitecore, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →