get_user_email_count_to_sheet
AI agents call get_user_email_count_to_sheet to retrieve information from GAM MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The name implies a read operation (getting email counts) combined with a write operation (outputting to a sheet). With no description available, confidence is low. The most severe applicable category would be Write, but 'get_' prefix strongly suggests a read/report operation. Given the sibling tools are all audit/read operations, this likely fits the Read or Write category.
From the tool's definition Tool name 'get_user_email_count_to_sheet' suggests retrieving email count data and writing it to a sheet, but the description is empty and uninformative.
Attacks that exploit this kind of access
get_user_email_count_to_sheet. It is categorised as a Read tool in the GAM MCP Server MCP Server, which means it retrieves data without modifying state.
Register the GAM MCP Server MCP server in PolicyLayer and add a rule for get_user_email_count_to_sheet: 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 GAM MCP Server. Nothing to install.
get_user_email_count_to_sheet 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 get_user_email_count_to_sheet 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 get_user_email_count_to_sheet. 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.
get_user_email_count_to_sheet is provided by the GAM MCP Server MCP server (ktibbs9417/gamcp). 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 →