diff_gtm_workspace_vs_live

Show CONFIG DRIFT between the draft workspace and the PUBLISHED (live) container version: which tags/triggers/variables the draft adds, removes or modifies, i.e. what publishing it would change.

SERVERSamarth Gtm Mcp SOURCEsamarth-gtm-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-samarthanalytics-sj-samarth-gtm-mcp/diff-gtm-workspace-vs-live.md

WHAT IT DOES

What diff_gtm_workspace_vs_live does on Samarth Gtm Mcp

AI agents call diff_gtm_workspace_vs_live to retrieve information from Samarth Gtm Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why diff_gtm_workspace_vs_live is rated Low

Compares configurations without modifying data; provides visibility into pending changes without executing them.

From the tool's definition Show CONFIG DRIFT between draft workspace and PUBLISHED container; what publishing would change.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs diff_gtm_workspace_vs_live 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 diff_gtm_workspace_vs_live, this is the rule to start with:

diff_gtm_workspace_vs_live Allowed

diff_gtm_workspace_vs_live is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "diff_gtm_workspace_vs_live": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Samarth Gtm Mcp, apply this rule, and every diff_gtm_workspace_vs_live call is checked against it from then on.

FAQ

Questions about diff_gtm_workspace_vs_live

What does the diff_gtm_workspace_vs_live tool do? +

Show CONFIG DRIFT between the draft workspace and the PUBLISHED (live) container version: which tags/triggers/variables the draft adds, removes or modifies, i.e. what publishing it would change. It is categorised as a Read tool in the Samarth Gtm Mcp MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on diff_gtm_workspace_vs_live? +

Register the Samarth Gtm MCP server in PolicyLayer and add a rule for diff_gtm_workspace_vs_live: 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.

What risk level is diff_gtm_workspace_vs_live? +

diff_gtm_workspace_vs_live is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit diff_gtm_workspace_vs_live? +

Yes. Add a rate_limit block to the diff_gtm_workspace_vs_live 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.

How do I block diff_gtm_workspace_vs_live completely? +

Set action: deny in the PolicyLayer policy for diff_gtm_workspace_vs_live. 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.

What MCP server provides diff_gtm_workspace_vs_live? +

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

KEEP EXPLORING

More on Samarth Gtm, and thousands of servers like it.

This server

All 236 Samarth Gtm tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →