Critical Risk

security-remove-role-member

Removes members from a Sitecore role.

Part of the Mcp Sitecore MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

@antonytm/mcp-sitecore-server Destructive Risk 4/5

AI agents may call security-remove-role-member to permanently remove or destroy resources in Mcp Sitecore. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. Intercept blocks destructive tools by default and requires explicit human approval before enabling them.

Without a policy, an AI agent could call security-remove-role-member in a loop, permanently destroying resources in Mcp Sitecore. There is no undo for destructive operations. Intercept blocks this tool by default and only allows it when a human explicitly approves the action.

Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.

io-github-antonytm-mcp-sitecore-server.yaml
tools:
  security-remove-role-member:
    rules:
      - action: deny
        reason: "Blocked by default — enable with approval"

See the full Mcp Sitecore policy for all 153 tools.

Tool Name security-remove-role-member
Category Destructive
Risk Level Critical

View all 153 tools →

What does the security-remove-role-member tool do? +

Removes members from 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.

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

Add a rule in your Intercept YAML policy under the tools section for security-remove-role-member. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Mcp Sitecore MCP server.

What risk level is security-remove-role-member? +

security-remove-role-member 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-role-member? +

Yes. Add a rate_limit block to the security-remove-role-member rule in your Intercept 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-role-member completely? +

Set action: deny in the Intercept policy for security-remove-role-member. 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-role-member? +

security-remove-role-member is provided by the Mcp Sitecore MCP server (@antonytm/mcp-sitecore-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Mcp Sitecore

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.