security-set-user · Sitecore MCP: Risk & Policy

WHAT IT DOES

What security-set-user does on SitecoreMCP

AI agents use security-set-user 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-set-user needs a policy

The tool modifies user account properties reversibly (passwords, roles, permissions, contact info, etc.) rather than deleting them. This is a Write operation. Severity is high because unauthorized modification of user accounts in an enterprise Sitecore system could grant an AI agent the ability to escalate privileges, create backdoor access, or compromise security posture.

From the tool's definition Tool name 'security-set-user' and description 'Updates properties of a Sitecore user account' indicate modification of user account data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

security-set-user Rate-limited

security-set-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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "security-set-user": {
      "limits": [
        {
          "counter": "security-set-user_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-set-user

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

Updates properties of a Sitecore user account. 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-set-user? +

Register the Sitecore MCP server in PolicyLayer and add a rule for security-set-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 SitecoreMCP. Nothing to install.

What risk level is security-set-user? +

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

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

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

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

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