Retrieve all Metabase users with their roles and permissions - use this to understand user access, manage permissions, or audit accounts
AI agents call list_users to retrieve information from Metabase 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 and queries user information from Metabase without creating, modifying, or deleting data. It is purely informational. However, severity is elevated to medium rather than low because the data retrieved (user identities, roles, and permissions) is sensitive and could inform privilege escalation or lateral movement attacks if an AI agent misuses it to systematically map organizational access…
From the tool's definition Tool description states 'Retrieve all Metabase users with their roles and permissions' - the verb 'Retrieve' and action of reading user data without modification indicates a read operation.
Attacks that exploit this kind of access
Retrieve all Metabase users with their roles and permissions - use this to understand user access, manage permissions, or audit accounts. It is categorised as a Read tool in the Metabase MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Metabase 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 Metabase 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 Metabase MCP Server MCP server (thangnm93/metabase-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 →