Retrieves the total number of emails received on a specific calendar day.
AI agents call google_gmails_get_counts to retrieve information from ContextCore MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only retrieves aggregate count data (total number of emails on a specific day) from Gmail. It performs no modifications, deletions, or external actions. The blast radius of misuse is minimal — at worst, an agent could repeatedly query email counts, which is noisy but not damaging. This is a straightforward Read operation.
From the tool's definition Tool name contains 'get' and description states 'Retrieves the total number of emails' — purely a query operation with no side effects.
Attacks that exploit this kind of access
Retrieves the total number of emails received on a specific calendar day. It is categorised as a Read tool in the ContextCore MCP MCP Server, which means it retrieves data without modifying state.
Register the ContextCore MCP server in PolicyLayer and add a rule for google_gmails_get_counts: 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 ContextCore MCP. Nothing to install.
google_gmails_get_counts 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 google_gmails_get_counts 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 google_gmails_get_counts. 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.
google_gmails_get_counts is provided by the ContextCore MCP server (rkpraveendev/contextcore-mcp). 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 →