Add a user to a group.
AI agents use add_group_user to create or update resources in Looker MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Looker MCP Server environment.
The tool creates or modifies group membership data (adding a user to a group). This is a reversible Write operation—the user can be removed from the group later. While it has administrative implications affecting access control and permissions, it does not delete data (Destructive), execute arbitrary code (Execute), or move money (Financial).
From the tool's definition Tool description: 'Add a user to a group.' This modifies group membership, a reversible administrative operation. The server context indicates user administration capabilities ('administering users').
Attacks that exploit this kind of access
Add a user to a group. It is categorised as a Write tool in the Looker MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Looker MCP Server MCP server in PolicyLayer and add a rule for add_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.
add_group_user is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the add_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 add_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.
add_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 →