Sets an access control entry to a Sitecore item by its path.
AI agents use security-set-item-acl-by-path to create or update resources in SitecoreMCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your SitecoreMCP environment.
This tool modifies access control settings on Sitecore items, which is a reversible but high-impact change to security policies. It falls under Write (creates/modifies data reversibly) rather than Execute because it directly configures permissions rather than executing arbitrary code.
From the tool's definition Tool name 'security-set-item-acl-by-path' explicitly states 'set' action on 'access control entry' (ACL) for a Sitecore item. Description confirms it 'Sets an access control entry' which modifies security permissions.
Attacks that exploit this kind of access
Sets an access control entry to a Sitecore item by its path. It is categorised as a Write tool in the SitecoreMCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Sitecore MCP server in PolicyLayer and add a rule for security-set-item-acl-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.
security-set-item-acl-by-path is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the security-set-item-acl-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 security-set-item-acl-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.
security-set-item-acl-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 →