ga4_update_property
[GA4 WRITE] Update a GA4 property (displayName / timeZone / currencyCode / industryCategory).
This record as markdown: /tools/io-github-samarthanalytics-sj-samarth-gtm-mcp/ga4-update-property.md
What ga4_update_property does on Samarth Gtm Mcp
AI agents use ga4_update_property 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 ga4_update_property is rated Medium
This tool creates or modifies data reversibly by updating GA4 property metadata. It does not delete data (would be Destructive), execute arbitrary code (would be Execute), or commit financial transactions (would be Financial). The server documentation notes 'gated writes' and 'audits', indicating write operations are present but controlled.
From the tool's definition Tool name contains '[GA4 WRITE]' prefix and description states 'Update a GA4 property' with modifiable fields (displayName, timeZone, currencyCode, industryCategory). These are reversible configuration changes.
Attacks that exploit this kind of access
The rule that runs ga4_update_property 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 ga4_update_property, this is the rule to start with:
ga4_update_property 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 ga4_update_property call is checked against it from then on.
Questions about ga4_update_property
[GA4 WRITE] Update a GA4 property (displayName / timeZone / currencyCode / industryCategory). 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 ga4_update_property: 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.
ga4_update_property 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_update_property 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_update_property. 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_update_property 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