AI agents call security-remove-role to permanently remove resources in Mcp Sitecore — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Removing a role is a destructive operation that cannot be undone without manual restoration. It impacts access control and security configuration. While not a direct data deletion, role removal is irreversible and affects system security posture, making it more severe than Write operations. The blast radius is high if an AI agent removes critical security roles unintentionally.
From the tool's definition Tool name includes 'remove' and description states 'Removes a Sitecore role' — this irreversibly deletes a role from the system.
Documented attack patterns abuse exactly the kind of access security-remove-role gives an agent:
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-role:
{
"version": "1",
"default": "deny",
"hide": [
"security-remove-role"
]
}security-remove-role disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Removes a Sitecore role. 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.
Register the Mcp Sitecore MCP server in PolicyLayer and add a rule for security-remove-role: 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.
security-remove-role is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the security-remove-role 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.
Set action: deny in the PolicyLayer policy for security-remove-role. 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.
security-remove-role 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.
Start from Mcp Sitecore, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
149 Mcp Sitecore tools catalogued and risk-classified — across an index of 43,000+ MCP servers.