Admin tool to list all registered users
AI agents call list_users to retrieve information from Gmail MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read/query operation (listing registered users), which typically falls under the Read category. However, the severity is elevated to 'high' rather than 'low' because: (1) it is explicitly an 'Admin tool', indicating privileged access; (2) listing all registered users in a Gmail integration server could expose sensitive information about user accounts and identity data; (3) an AI agent with…
From the tool's definition Tool name: 'list_users'; description: 'Admin tool to list all registered users'. This retrieves a list of registered users without modifying data.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
Admin tool to list all registered users. It is categorised as a Read tool in the Gmail MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Gmail 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 Gmail 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 Gmail MCP Server MCP server (kushal45/gmailmcpserver). 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 →