List all users in the Looker instance.
AI agents call list_users to retrieve information from Looker MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves user information from the Looker instance without creating, modifying, deleting, or executing any operations. It is a pure read operation that queries existing data. Severity is low because while user lists may contain organizational information, listing users is a standard query operation without side effects or data mutation.
From the tool's definition Tool name is 'list_users' and description states 'List all users in the Looker instance.' The verb 'list' and action of querying/retrieving user data with no modification indicates a read-only operation.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
List all users in the Looker instance. It is categorised as a Read tool in the Looker MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Looker MCP Server MCP server in PolicyLayer and add a rule for list_users: 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.
list_users is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_users 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 list_users. 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.
list_users 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 →