Fallback: PATCH/POST/DELETE any GA4 Admin API endpoint not covered by named tools. Use only when no named tool exists. Prefer ga4.conversion_events.create/delete, ga4.custom_dimensions.create, ga4.custom_metrics.create. Requires confirm_passthrough=true. Dry-run by default.
AI agents call ga4.passthrough.write to permanently remove resources in Ads — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This is a passthrough tool that permits DELETE operations on GA4 Admin API endpoints with minimal constraints. Although it defaults to dry-run mode, the actual execution via confirm_passthrough=true enables irreversible deletions of analytics resources such as conversion events, custom dimensions, custom metrics, and data streams.
From the tool's definition Tool description explicitly lists 'DELETE' capability and states 'Fallback: PATCH/POST/DELETE any GA4 Admin API endpoint'.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
Fallback: PATCH/POST/DELETE any GA4 Admin API endpoint not covered by named tools. Use only when no named tool exists. Prefer ga4.conversion_events.create/delete, ga4.custom_dimensions.create, ga4.custom_metrics.create. Requires confirm_passthrough=true. Dry-run by default. It is categorised as a Destructive tool in the Ads MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Ads MCP server in PolicyLayer and add a rule for ga4.passthrough.write: 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.passthrough.write is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the ga4.passthrough.write 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.passthrough.write. 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.passthrough.write 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 →