ga_send_login · MCP Google Analytics Server MCP

WHAT IT DOES

What ga_send_login does on MCP Google Analytics Server

AI agents use ga_send_login 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.

WHY IT NEEDS A POLICY

Why ga_send_login needs a policy

This tool creates a new event record in Google Analytics. While login events are standard telemetry and not inherently dangerous, sending arbitrary login events could be misused to pollute analytics data, create false user engagement signals, or trigger downstream automation based on login events. The impact is reversible (events can be filtered or deleted), making it Write rather than Destructive.

From the tool's definition Tool description states 'Send a login event to Google Analytics' - the word 'send' indicates data is being written/created in Google Analytics. This is a data modification operation through the Measurement Protocol.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

ga_send_login Rate-limited

ga_send_login stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "ga_send_login": {
      "limits": [
        {
          "counter": "ga_send_login_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches MCP Google Analytics Server, so you can run agents against it safely.

FAQ

Questions about ga_send_login

What does the ga_send_login tool do? +

Send a login event to Google Analytics. Standard event for tracking user logins with authentication method. 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.

How do I enforce a policy on ga_send_login? +

Register the MCP Google Analytics Server MCP server in PolicyLayer and add a rule for ga_send_login: 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.

What risk level is ga_send_login? +

ga_send_login is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit ga_send_login? +

Yes. Add a rate_limit block to the ga_send_login 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.

How do I block ga_send_login completely? +

Set action: deny in the PolicyLayer policy for ga_send_login. 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.

What MCP server provides ga_send_login? +

ga_send_login 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.