security-remove-user

THE RISK

Critical Risk

Why security-remove-user needs a policy

Removing a user is a destructive action that cannot be easily undone and permanently eliminates access credentials and associated permissions. This is more severe than a write operation because the action is irreversible. In the context of a content management system like Sitecore, user removal could impact multiple systems and require administrative recovery steps.

From the tool's definition Tool name 'security-remove-user' and description 'Removes the Sitecore user' indicate irreversible deletion of a user account.

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

POLICY

How to control security-remove-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-remove-user:

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "security-remove-user"
  ]
}

security-remove-user disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

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.

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

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in Mcp Sitecore → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about security-remove-user

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

Removes the Sitecore user. It is categorised as a Destructive tool in the Mcp Sitecore MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on security-remove-user? +

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

security-remove-user is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

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

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

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

security-remove-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 →