Removes a Sitecore role.
AI agents call security-remove-role to permanently remove resources in SitecoreMCP — 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 or backup recovery. It irreversibly deletes security configuration and could impact multiple users whose permissions depend on that role. This qualifies as Destructive rather than Write because the action cannot be reversed through normal tool operations.
From the tool's definition Tool name explicitly states 'remove-role' and description confirms it 'Removes a Sitecore role.' The verb 'remove' in a security context indicates irreversible deletion of a role object.
Attacks that exploit this kind of access
Removes a Sitecore role. It is categorised as a Destructive tool in the SitecoreMCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the 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 SitecoreMCP. 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 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →