List all labels with their message counts
AI agents call gmail.listLabels 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 retrieves and lists existing labels along with their message counts. It performs no side effects, does not modify, delete, or execute any operations. It is a straightforward query operation that returns information about the user's Gmail label organization. The low severity reflects minimal blast radius—an agent misusing this tool could only over-retrieve label information, not cause meaningful harm.
From the tool's definition Tool name 'listLabels' and description 'List all labels with their message counts' indicate a read-only retrieval operation that queries label metadata without modifying data.
Attacks that exploit this kind of access
List all labels with their message counts. 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 gmail.listLabels: 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.
gmail.listLabels 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 gmail.listLabels 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 gmail.listLabels. 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.
gmail.listLabels is provided by the Gmail MCP Server MCP server (shcallaway/gmail-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 →