spy_gtag_config
Read the PUBLIC gtag.js tag configuration for ANY measurement id (yours or a competitor - no GA4 access needed): enhanced-measurement toggles, tag-level key events, user-provided data collection, email redaction, Google Signals region scope, linked destinations (GT-/AW-), server container URL (sG...
This record as markdown: /tools/io-github-samarthanalytics-sj-samarth-gtm-mcp/spy-gtag-config.md
What spy_gtag_config does on Samarth Gtm Mcp
AI agents call spy_gtag_config to retrieve information from Samarth Gtm Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why spy_gtag_config is rated Low
Retrieves publicly accessible gtag configuration data without modification or execution capabilities, but enables competitor reconnaissance.
From the tool's definition Read the PUBLIC gtag.js tag configuration for ANY measurement id (yours or a competitor)
Attacks that exploit this kind of access
The rule that runs spy_gtag_config 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 spy_gtag_config, this is the rule to start with:
spy_gtag_config is read-only, so it stays allowed. 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 spy_gtag_config call is checked against it from then on.
Questions about spy_gtag_config
Read the PUBLIC gtag.js tag configuration for ANY measurement id (yours or a competitor - no GA4 access needed): enhanced-measurement toggles, tag-level key events, user-provided data collection, email redaction, Google Signals region scope, linked destinations (GT-/AW-), server container URL (sGTM), session timeout, cross-domain linker domains. Config the tag does not carry (property settings, reporting data) is NOT included - say so instead of guessing. It is categorised as a Read tool in the Samarth Gtm Mcp MCP Server, which means it retrieves data without modifying state.
Register the Samarth Gtm MCP server in PolicyLayer and add a rule for spy_gtag_config: 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.
spy_gtag_config is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the spy_gtag_config 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 spy_gtag_config. 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.
spy_gtag_config 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