Send a sign-up event to Google Analytics. Standard event for tracking new user registrations.
AI agents use ga_send_signup to create or update resources in MCP Google Analytics Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Google Analytics Server environment.
This tool modifies analytics data by creating a new event record (a sign-up event) in Google Analytics, which is a reversible write operation. It does not execute arbitrary code, delete data, or move money.
From the tool's definition Tool sends a sign-up event to Google Analytics, which creates/records a new event entry in the analytics system. The description explicitly states it is a 'standard event for tracking new user registrations,' indicating it writes event data to GA4.
Attacks that exploit this kind of access
Send a sign-up event to Google Analytics. Standard event for tracking new user registrations. It is categorised as a Write tool in the MCP Google Analytics Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Google Analytics Server MCP server in PolicyLayer and add a rule for ga_send_signup: 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 MCP Google Analytics Server. Nothing to install.
ga_send_signup is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the ga_send_signup 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 ga_send_signup. 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.
ga_send_signup is provided by the MCP Google Analytics Server MCP server (leosepulveda/mcp-google-analytics). 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 →