setup_server_ecommerce_funnel
ONE STEP: install the server-side ecommerce funnel in a SERVER container (containerId must be the SERVER one). Per funnel event (default the standard 7) it creates a trigger ({{_event}} equals the event, scoped to the GA4 client) plus a GA4 server tag relaying it, and with adsConversionId plus a ...
This record as markdown: /tools/io-github-samarthanalytics-sj-samarth-gtm-mcp/setup-server-ecommerce-funnel.md
What setup_server_ecommerce_funnel does on Samarth Gtm Mcp
AI agents use setup_server_ecommerce_funnel 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 setup_server_ecommerce_funnel is rated Medium
Creates and modifies GTM container infrastructure, triggers, and conversion tags; reversible but high-impact configuration changes.
From the tool's definition install, creates triggers, creates tags, relaying, Enables
Attacks that exploit this kind of access
The rule that runs setup_server_ecommerce_funnel 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 setup_server_ecommerce_funnel, this is the rule to start with:
setup_server_ecommerce_funnel 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 setup_server_ecommerce_funnel call is checked against it from then on.
Questions about setup_server_ecommerce_funnel
ONE STEP: install the server-side ecommerce funnel in a SERVER container (containerId must be the SERVER one). Per funnel event (default the standard 7) it creates a trigger ({{_event}} equals the event, scoped to the GA4 client) plus a GA4 server tag relaying it, and with adsConversionId plus a per-event conversionLabel, a Google Ads conversion server tag for that event (typically purchase). Enables the Client Name built-in. Idempotent by name. Run AFTER create_server_container_from_web. 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 setup_server_ecommerce_funnel: 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.
setup_server_ecommerce_funnel 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 setup_server_ecommerce_funnel 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 setup_server_ecommerce_funnel. 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.
setup_server_ecommerce_funnel 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