Removes a Sitecore domain.
AI agents call security-remove-domain 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 domain from a Sitecore system is a destructive operation that permanently deletes domain configuration and likely impacts authentication, security policies, and user access controls. This is irreversible and has a significant blast radius in an enterprise environment. It is more severe than Write (which is reversible modification) and qualifies as Destructive per the classification rules.
From the tool's definition Tool name explicitly states 'remove' and description states 'Removes a Sitecore domain' — this is irreversible deletion of a domain configuration that cannot be undone without manual restoration.
Attacks that exploit this kind of access
Removes a Sitecore domain. 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-domain: 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-domain 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-domain 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-domain. 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-domain 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 →