create_stape_data_pipeline
ONE STEP: stand up the Stape Data Tag -> Data Client enrichment pipeline that RAISES Meta CAPI Event Match Quality. In the WEB container it creates a Data Tag (stape-io/data-tag, imported automatically) firing on All Pages that posts full first-party identity (em/ph/fbp/fbc/IP/UA + dataLayer + co...
This record as markdown: /tools/io-github-samarthanalytics-sj-samarth-gtm-mcp/create-stape-data-pipeline.md
What create_stape_data_pipeline does on Samarth Gtm Mcp
AI agents use create_stape_data_pipeline 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_stape_data_pipeline is rated Medium
Creates new tags and modifies container configuration; reversible but affects data collection pipeline with privacy implications.
From the tool's definition creates Data Tag and Data Client, posts identity data, persists against cookie
Attacks that exploit this kind of access
The rule that runs create_stape_data_pipeline 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_stape_data_pipeline, this is the rule to start with:
create_stape_data_pipeline 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_stape_data_pipeline call is checked against it from then on.
Questions about create_stape_data_pipeline
ONE STEP: stand up the Stape Data Tag -> Data Client enrichment pipeline that RAISES Meta CAPI Event Match Quality. In the WEB container it creates a Data Tag (stape-io/data-tag, imported automatically) firing on All Pages that posts full first-party identity (em/ph/fbp/fbc/IP/UA + dataLayer + consent) to <serverUrl>/data; in the SERVER container it creates a Data Client (stape-io/data-client) that claims /data and PERSISTS that identity against a first-party client-id cookie - so a later conversion that arrives WITHOUT identity still matches. serverUrl is the deployed tagging-server URL. Idempotent: an existing Data Tag / Data Client is reused. Does NOT deploy the host and does NOT publish. AFTER this, build the Meta CAPI tag with create_meta_capi_server_tag (mapEmqVariables on) so its user_data reads the enriched event; RELAY the returned note + nextSteps to the user. 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_stape_data_pipeline: 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_stape_data_pipeline 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_stape_data_pipeline 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_stape_data_pipeline. 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_stape_data_pipeline 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