Remove a user from a group.
AI agents call remove_group_user to permanently remove resources in Looker MCP Server — 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 is a destructive, hard-to-reverse action with potentially wide blast radius: the user may lose access to dashboards, content, and data governed by group-based permissions. This is more severe than a simple write/update and aligns with the Destructive category.
From the tool's definition 'Remove a user from a group' — removal of group membership is irreversible without a corresponding re-add operation, and losing group membership can revoke access permissions across the Looker instance.
Attacks that exploit this kind of access
Remove a user from a group. It is categorised as a Destructive tool in the Looker MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Looker MCP Server MCP server in PolicyLayer and add a rule for remove_group_user: 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 Looker MCP Server. Nothing to install.
remove_group_user 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_user 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_user. 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_user is provided by the Looker MCP Server MCP server (ultrathink-solutions/looker-mcp-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 →