audit_install_drift
Report DRIFT against the install manifest, the record of resources our setup tools (e.g. setup_ecommerce_funnel) created here. Compares each managed tag/trigger/variable to the LIVE container: INTACT, MODIFIED (renamed or reconfigured since setup), DELETED; and lists UNMANAGED resources added out...
This record as markdown: /tools/io-github-samarthanalytics-sj-samarth-gtm-mcp/audit-install-drift.md
What audit_install_drift does on Samarth Gtm Mcp
AI agents use audit_install_drift 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 audit_install_drift is rated Medium
An AI agent can call audit_install_drift faster than any human can review: one bad instruction and it creates or modifies resources in Samarth Gtm Mcp by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs audit_install_drift 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 audit_install_drift, this is the rule to start with:
audit_install_drift 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 audit_install_drift call is checked against it from then on.
Questions about audit_install_drift
Report DRIFT against the install manifest, the record of resources our setup tools (e.g. setup_ecommerce_funnel) created here. Compares each managed tag/trigger/variable to the LIVE container: INTACT, MODIFIED (renamed or reconfigured since setup), DELETED; and lists UNMANAGED resources added outside our setup. Read-only. Returns hasManifest:false when no setup has been recorded yet. 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 audit_install_drift: 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.
audit_install_drift 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 audit_install_drift 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 audit_install_drift. 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.
audit_install_drift 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