AI agents use ga4.conversion_events.create to create or update resources in Ads — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ads environment.
This tool creates/marks a conversion event in GA4, which is a reversible write operation (there is a corresponding delete tool on the server). It modifies GA4 property configuration but does not delete data, execute code, or move money. Misuse could affect conversion tracking and downstream reporting/bidding decisions, hence medium severity.
From the tool's definition Mark an event as a conversion event on the configured GA4 property
Attacks that exploit this kind of access
Mark an event as a conversion event on the configured GA4 property. It is categorised as a Write tool in the Ads MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Ads MCP server in PolicyLayer and add a rule for ga4.conversion_events.create: 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 Ads. Nothing to install.
ga4.conversion_events.create 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 ga4.conversion_events.create 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 ga4.conversion_events.create. 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.
ga4.conversion_events.create is provided by the Ads MCP server (manlikemuneeb/ads-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 →