# 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.

Agent View of the PolicyLayer registry record for `create_stape_data_pipeline`. HTML page: https://policylayer.com/tools/io-github-samarthanalytics-sj-samarth-gtm-mcp/create-stape-data-pipeline

## Facts

- Tool: `create_stape_data_pipeline`
- Server: Samarth Gtm Mcp (`samarth-gtm-mcp`) — https://policylayer.com/tools/io-github-samarthanalytics-sj-samarth-gtm-mcp.md
- Install: `npx -y samarth-gtm-mcp`
- Homepage: https://github.com/samarthanalytics-sj/samarth-analytics-mcp
- Risk category: Write (Medium risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Rate-limited

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "create_stape_data_pipeline",
    "arguments": {}
  }
}
```

## 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 own definition: "creates Data Tag and Data Client, posts identity data, persists against cookie"

## Use case

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.

## Recommended policy (PolicyLayer)

Verdict: **Rate-limited**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Samarth Gtm Mcp:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_stape_data_pipeline": {
      "limits": [
        {
          "counter": "create_stape_data_pipeline_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## Other tools on Samarth Gtm Mcp (253)

- `built_in_variables_disable` — Destructive — https://policylayer.com/tools/io-github-samarthanalytics-sj-samarth-gtm-mcp/built-in-variables-disable.md
- `delete_ga4_account` — Destructive — https://policylayer.com/tools/io-github-samarthanalytics-sj-samarth-gtm-mcp/delete-ga4-account.md
- `delete_ga4_property` — Destructive — https://policylayer.com/tools/io-github-samarthanalytics-sj-samarth-gtm-mcp/delete-ga4-property.md
- `delete_gtm_client` — Destructive — https://policylayer.com/tools/io-github-samarthanalytics-sj-samarth-gtm-mcp/delete-gtm-client.md
- `delete_gtm_folder` — Destructive — https://policylayer.com/tools/io-github-samarthanalytics-sj-samarth-gtm-mcp/delete-gtm-folder.md
- `delete_gtm_tag` — Destructive — https://policylayer.com/tools/io-github-samarthanalytics-sj-samarth-gtm-mcp/delete-gtm-tag.md
- `delete_gtm_trigger` — Destructive — https://policylayer.com/tools/io-github-samarthanalytics-sj-samarth-gtm-mcp/delete-gtm-trigger.md
- `delete_gtm_variable` — Destructive — https://policylayer.com/tools/io-github-samarthanalytics-sj-samarth-gtm-mcp/delete-gtm-variable.md
- `delete_unused_gtm_triggers` — Destructive — https://policylayer.com/tools/io-github-samarthanalytics-sj-samarth-gtm-mcp/delete-unused-gtm-triggers.md
- `delete_unused_gtm_variables` — Destructive — https://policylayer.com/tools/io-github-samarthanalytics-sj-samarth-gtm-mcp/delete-unused-gtm-variables.md
- `environments_delete` — Destructive — https://policylayer.com/tools/io-github-samarthanalytics-sj-samarth-gtm-mcp/environments-delete.md
- `folders_delete` — Destructive — https://policylayer.com/tools/io-github-samarthanalytics-sj-samarth-gtm-mcp/folders-delete.md
- `forget_memory` — Destructive — https://policylayer.com/tools/io-github-samarthanalytics-sj-samarth-gtm-mcp/forget-memory.md
- `ga4_delete_account` — Destructive — https://policylayer.com/tools/io-github-samarthanalytics-sj-samarth-gtm-mcp/ga4-delete-account.md
- `ga4_delete_property` — Destructive — https://policylayer.com/tools/io-github-samarthanalytics-sj-samarth-gtm-mcp/ga4-delete-property.md
- `tags_delete` — Destructive — https://policylayer.com/tools/io-github-samarthanalytics-sj-samarth-gtm-mcp/tags-delete.md
- `triggers_delete` — Destructive — https://policylayer.com/tools/io-github-samarthanalytics-sj-samarth-gtm-mcp/triggers-delete.md
- `user_permissions_delete` — Destructive — https://policylayer.com/tools/io-github-samarthanalytics-sj-samarth-gtm-mcp/user-permissions-delete.md
- `variables_delete` — Destructive — https://policylayer.com/tools/io-github-samarthanalytics-sj-samarth-gtm-mcp/variables-delete.md
- `versions_delete` — Destructive — https://policylayer.com/tools/io-github-samarthanalytics-sj-samarth-gtm-mcp/versions-delete.md
- `consent_compliance_audit` — Execute — https://policylayer.com/tools/io-github-samarthanalytics-sj-samarth-gtm-mcp/consent-compliance-audit.md
- `consent_scenario_capture` — Execute — https://policylayer.com/tools/io-github-samarthanalytics-sj-samarth-gtm-mcp/consent-scenario-capture.md
- `environments_reauthorize` — Execute — https://policylayer.com/tools/io-github-samarthanalytics-sj-samarth-gtm-mcp/environments-reauthorize.md
- `probe_server_runtime` — Execute — https://policylayer.com/tools/io-github-samarthanalytics-sj-samarth-gtm-mcp/probe-server-runtime.md
- `run_ga4_report` — Execute — https://policylayer.com/tools/io-github-samarthanalytics-sj-samarth-gtm-mcp/run-ga4-report.md
- `runtime_synthetic_test` — Execute — https://policylayer.com/tools/io-github-samarthanalytics-sj-samarth-gtm-mcp/runtime-synthetic-test.md
- `site_crawl` — Execute — https://policylayer.com/tools/io-github-samarthanalytics-sj-samarth-gtm-mcp/site-crawl.md
- `suggest_tags_from_url` — Execute — https://policylayer.com/tools/io-github-samarthanalytics-sj-samarth-gtm-mcp/suggest-tags-from-url.md
- `versions_publish` — Execute — https://policylayer.com/tools/io-github-samarthanalytics-sj-samarth-gtm-mcp/versions-publish.md
- `workspace_create_version_and_publish` — Execute — https://policylayer.com/tools/io-github-samarthanalytics-sj-samarth-gtm-mcp/workspace-create-version-and-publish.md
- …and 223 more: https://policylayer.com/tools/io-github-samarthanalytics-sj-samarth-gtm-mcp.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=io-github-samarthanalytics-sj-samarth-gtm-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/io-github-samarthanalytics-sj-samarth-gtm-mcp