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

WHAT IT DOES

What security-lock-item-by-id does on SitecoreMCP

AI agents use security-lock-item-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-lock-item-by-id needs a policy

Locking an item is a reversible modification that changes access/editing permissions for a content item. While it restricts others' ability to edit, the lock itself can be released, making it Write rather than Destructive. The severity is medium because misuse could block legitimate content editors from their work, but the impact is temporary and recoverable.

From the tool's definition Tool name includes 'lock' which modifies item state; description states 'Lock a Sitecore item by its ID', indicating a state change operation that prevents concurrent editing.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

security-lock-item-by-id Rate-limited

security-lock-item-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-lock-item-by-id": {
      "limits": [
        {
          "counter": "security-lock-item-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-lock-item-by-id

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

Lock 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-lock-item-by-id? +

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

security-lock-item-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-lock-item-by-id? +

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

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

security-lock-item-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.