Remove a user from a group (requires WRITE_ENABLED=true)
AI agents call remove_user_from_group to permanently remove resources in ServiceNow-MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Removing a user from a group revokes their access and permissions associated with that group. While technically a modification (Write), removing access control membership can have significant security and operational consequences that may be difficult to fully reverse (especially if the removal is not logged or noticed).
From the tool's definition 'Remove a user from a group' — removing group membership is a potentially irreversible access control change; requires WRITE_ENABLED=true
Attacks that exploit this kind of access
Remove a user from a group (requires WRITE_ENABLED=true). It is categorised as a Destructive tool in the ServiceNow-MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the ServiceNow- MCP server in PolicyLayer and add a rule for remove_user_from_group: 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 ServiceNow-MCP. Nothing to install.
remove_user_from_group 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 remove_user_from_group 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 remove_user_from_group. 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.
remove_user_from_group is provided by the ServiceNow- MCP server (tedorigawa001/servicenow-mcp). 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 →