set_ga4_measurement_id
Set/replace the Measurement ID on ONE GA4 tag. The value may be a literal id (G-/AW-/GT-XXXX) or a GTM variable like {{GA4 Variable}}. For a GA4 Event tag (gaawe) it sets measurementIdOverride; for a Google tag (googtag) it sets the tag ID. It builds the parameter correctly and preserves the rest...
This record as markdown: /tools/io-github-samarthanalytics-sj-samarth-gtm-mcp/set-ga4-measurement-id.md
What set_ga4_measurement_id does on Samarth Gtm Mcp
AI agents use set_ga4_measurement_id to create or update resources in Samarth Gtm Mcp, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Samarth Gtm Mcp environment.
Why set_ga4_measurement_id is rated Medium
Modifies GA4 tag configuration reversibly; impacts analytics data collection scope but not destructively.
From the tool's definition Set/replace the Measurement ID on ONE GA4 tag, builds the parameter correctly.
Attacks that exploit this kind of access
The rule that runs set_ga4_measurement_id safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Samarth Gtm Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For set_ga4_measurement_id, this is the rule to start with:
set_ga4_measurement_id 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Samarth Gtm Mcp, apply this rule, and every set_ga4_measurement_id call is checked against it from then on.
Questions about set_ga4_measurement_id
Set/replace the Measurement ID on ONE GA4 tag. The value may be a literal id (G-/AW-/GT-XXXX) or a GTM variable like {{GA4 Variable}}. For a GA4 Event tag (gaawe) it sets measurementIdOverride; for a Google tag (googtag) it sets the tag ID. It builds the parameter correctly and preserves the rest of the tag, avoiding the. It is categorised as a Write tool in the Samarth Gtm Mcp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Samarth Gtm MCP server in PolicyLayer and add a rule for set_ga4_measurement_id: 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 Samarth Gtm Mcp. Nothing to install.
set_ga4_measurement_id 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 set_ga4_measurement_id 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 set_ga4_measurement_id. 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.
set_ga4_measurement_id is provided by the Samarth Gtm MCP server (samarth-gtm-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Samarth Gtm, and thousands of servers like it.
This server
Across the catalogue