create_meta_capi_server_tag
Create a Meta/Facebook Conversions API (CAPI) SERVER tag from the Stape template (stape-io / facebook-tag), imported automatically. containerId must be the SERVER container. Tuned for high Event Match Quality: action source website, Event Enhancement (gtmeec) ON, generate _fbp ON, and the EMQ use...
This record as markdown: /tools/io-github-samarthanalytics-sj-samarth-gtm-mcp/create-meta-capi-server-tag.md
What create_meta_capi_server_tag does on Samarth Gtm Mcp
AI agents use create_meta_capi_server_tag 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_meta_capi_server_tag is rated Medium
Creates GTM tag configuration that modifies tracking infrastructure and maps sensitive user data to third-party platform.
From the tool's definition Create Meta Conversions API SERVER tag, auto-mapped variables, external_id user_data
Attacks that exploit this kind of access
The rule that runs create_meta_capi_server_tag 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_meta_capi_server_tag, this is the rule to start with:
create_meta_capi_server_tag 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_meta_capi_server_tag call is checked against it from then on.
Questions about create_meta_capi_server_tag
Create a Meta/Facebook Conversions API (CAPI) SERVER tag from the Stape template (stape-io / facebook-tag), imported automatically. containerId must be the SERVER container. Tuned for high Event Match Quality: action source website, Event Enhancement (gtmeec) ON, generate _fbp ON, and the EMQ user_data (em/ph/external_id plus client_ip_address/client_user_agent), ecommerce custom_data and event_id AUTO-MAPPED from {{ed - }} variables that are created if missing, so ONE call yields a working tag; mapEmqVariables=false skips that mapping and the template still auto-extracts user data from the event. pixelId and accessToken are usually {{variables}}. 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_meta_capi_server_tag: 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_meta_capi_server_tag 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_meta_capi_server_tag 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_meta_capi_server_tag. 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_meta_capi_server_tag 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