create_server_container_from_web
ONE STEP: create a complete, production-shaped server-side container FROM a web container. Derives its GA4 Measurement ID and builds the SERVER container, a GA4 client with server-managed first-party FPID cookies, an all-events firing trigger, a GA4 relay tag, a GTM client that first-party-serves...
This record as markdown: /tools/io-github-samarthanalytics-sj-samarth-gtm-mcp/create-server-container-from-web.md
What create_server_container_from_web does on Samarth Gtm Mcp
AI agents use create_server_container_from_web 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 create_server_container_from_web is rated Medium
Creates production infrastructure spanning containers, tags, and tracking setup with persistent effects requiring manual reversal.
From the tool's definition create_server_container_from_web, builds SERVER container, GA4 relay tag, GTM client, first-party cookies
Attacks that exploit this kind of access
The rule that runs create_server_container_from_web 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 create_server_container_from_web, this is the rule to start with:
create_server_container_from_web 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 create_server_container_from_web call is checked against it from then on.
Questions about create_server_container_from_web
ONE STEP: create a complete, production-shaped server-side container FROM a web container. Derives its GA4 Measurement ID and builds the SERVER container, a GA4 client with server-managed first-party FPID cookies, an all-events firing trigger, a GA4 relay tag, a GTM client that first-party-serves the web container, and the standard Event Data variables (ed - event_id for browser/server dedup, ed - page_location for page-scoped triggers). With. 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 create_server_container_from_web: 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.
create_server_container_from_web 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 create_server_container_from_web 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 create_server_container_from_web. 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.
create_server_container_from_web 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