security-unlock-user

THE RISK

Medium Risk

Why security-unlock-user needs a policy

This tool changes user account status irreversibly in terms of time (an unlock persists until re-locked), but the operation itself is not destructive—data is not deleted or permanently lost. It is Write rather than Execute because it directly modifies a specific account attribute rather than executing arbitrary code.

From the tool's definition Unlocks a Sitecore user account that has been locked out due to failed login attempts. This modifies user account state (locked → unlocked) but is reversible; the account can be locked again.

Documented attack patterns abuse exactly the kind of access security-unlock-user gives an agent:

POLICY

How to control security-unlock-user

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 security-unlock-user:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "security-unlock-user": {
      "limits": [
        {
          "counter": "security-unlock-user_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

security-unlock-user 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.

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.

LIMIT 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 →

Write tools on other servers

M-Team MCP Server download_torrent YouTube MCP Server generate_video_title Android Forensics ADB MCP Server combine_reports 0xarchive web3_signup

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Argument validation → Checking tool call arguments against schema and policy before they run.
Scoped token → Per-person credentials that grant a defined subset of servers and tools.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about security-unlock-user

What does the security-unlock-user tool do? +

Unlocks a Sitecore user account that has been locked out due to failed login attempts. It is categorised as a Write tool in the Mcp Sitecore 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-unlock-user? +

Register the Mcp Sitecore MCP server in PolicyLayer and add a rule for security-unlock-user: 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 security-unlock-user? +

security-unlock-user is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit security-unlock-user? +

Yes. Add a rate_limit block to the security-unlock-user 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-unlock-user completely? +

Set action: deny in the PolicyLayer policy for security-unlock-user. 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-unlock-user? +

security-unlock-user 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 →