Returns whether the current user has Gmail connected
AI agents call gmail.status 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 is a simple status check that queries whether Gmail is connected for the current user. It has no capability to modify, execute operations, delete data, or affect finances. It merely retrieves status information, making it a Read operation with low severity - even if misused, an AI agent can only learn connection state, which carries minimal risk.
From the tool's definition The tool 'gmail.status' returns connection status information - a query operation that retrieves state data without side effects. The description explicitly states it 'returns whether the current user has Gmail connected', which is a read-only check.
Attacks that exploit this kind of access
Returns whether the current user has Gmail connected. 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.status: 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.status 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.status 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.status. 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.status 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 →