verify_tracking_setup
READ-ONLY post-install QA on the WEB container: verify a tracking setup against the funnel checklist, pass/warn/fail per check. Web: Google tag present, per-event GA4 tag coverage (exists, not paused, has a trigger, forwards the ecommerce object), consent defaults on Consent Initialization, web-t...
This record as markdown: /tools/io-github-samarthanalytics-sj-samarth-gtm-mcp/verify-tracking-setup.md
What verify_tracking_setup does on Samarth Gtm Mcp
AI agents call verify_tracking_setup 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 verify_tracking_setup is rated Low
Tool performs read-only verification and audit checks against tracking configuration without modifying data or triggering external operations.
From the tool's definition READ-ONLY post-install QA, verify tracking setup, pass/warn/fail per check
Attacks that exploit this kind of access
The rule that runs verify_tracking_setup 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 verify_tracking_setup, this is the rule to start with:
verify_tracking_setup 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 verify_tracking_setup call is checked against it from then on.
Questions about verify_tracking_setup
READ-ONLY post-install QA on the WEB container: verify a tracking setup against the funnel checklist, pass/warn/fail per check. Web: Google tag present, per-event GA4 tag coverage (exists, not paused, has a trigger, forwards the ecommerce object), consent defaults on Consent Initialization, web-to-server link. Per-event contract checks: TAXONOMY (reserved google_/ga_/firebase_ or malformed names GA4 rejects) and SCHEMA (required GA4 params per recommended event; for a tag forwarding the whole ecommerce object it names the params the site must push, since that is a runtime check). Given the server ids it also checks the GA4 client, the recorded tagging server URL, per-event relay coverage (a base all-events relay counts) and a LIVE /healthy probe. Run after the setup_ tools, and before telling the user tracking is complete. 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 verify_tracking_setup: 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.
verify_tracking_setup 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 verify_tracking_setup 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 verify_tracking_setup. 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.
verify_tracking_setup 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