security-add-item-acl-by-id · Sitecore MCP: Risk & Policy

WHAT IT DOES

What security-add-item-acl-by-id does on SitecoreMCP

AI agents use security-add-item-acl-by-id 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.

WHY IT NEEDS A POLICY

Why security-add-item-acl-by-id needs a policy

This tool creates or modifies access control entries, which is a Write operation. It's high severity because misconfigured ACLs could grant unintended permissions to sensitive content or restrict legitimate access, affecting security posture across the CMS. The operation is reversible (entries can be modified or removed), so it's not Destructive.

From the tool's definition Tool name contains 'add' and description states 'Adds an access control entry to a Sitecore item by its ID.' This modifies ACL (access control list) data on an item, which is a reversible configuration change.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

security-add-item-acl-by-id Rate-limited

security-add-item-acl-by-id stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "security-add-item-acl-by-id": {
      "limits": [
        {
          "counter": "security-add-item-acl-by-id_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches SitecoreMCP, so you can run agents against it safely.

FAQ

Questions about security-add-item-acl-by-id

What does the security-add-item-acl-by-id tool do? +

Adds an access control entry to a Sitecore item by its ID. 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.

How do I enforce a policy on security-add-item-acl-by-id? +

Register the Sitecore MCP server in PolicyLayer and add a rule for security-add-item-acl-by-id: 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 security-add-item-acl-by-id? +

security-add-item-acl-by-id is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit security-add-item-acl-by-id? +

Yes. Add a rate_limit block to the security-add-item-acl-by-id 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 security-add-item-acl-by-id completely? +

Set action: deny in the PolicyLayer policy for security-add-item-acl-by-id. 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 security-add-item-acl-by-id? +

security-add-item-acl-by-id 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.