AI agents call remove_group_members to permanently remove resources in Snow — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Removing users from a group revokes their access permissions and group memberships. While theoretically reversible by re-adding members, in practice this is a destructive access-control operation with high blast radius: bulk removal ('multiple users') could instantly lock out many users from ITSM workflows, on-call rotations, or approval chains. This warrants Destructive classification at high severity.
From the tool's definition "Remove multiple users from a group" — removing members is an irreversible or difficult-to-reverse access control change affecting potentially many users at once.
Documented attack patterns abuse exactly the kind of access remove_group_members gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Snow, and nothing reaches the server without passing your rules. This is the rule we recommend for remove_group_members:
{
"version": "1",
"default": "deny",
"hide": [
"remove_group_members"
]
}remove_group_members 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.
Remove multiple users from a group. It is categorised as a Destructive tool in the Snow MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Snow MCP server in PolicyLayer and add a rule for remove_group_members: 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 Snow. Nothing to install.
remove_group_members 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_group_members 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_group_members. 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_group_members is provided by the Snow MCP server (shunyaai/snow-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Snow, 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.
88 Snow tools catalogued and risk-classified — across an index of 43,000+ MCP servers.