New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

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

SERVERSamarth Gtm Mcp SOURCEsamarth-gtm-mcp
Medium RISK CLASS
Category Write
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

Questions about audit_install_drift

What does the audit_install_drift tool do? +

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.

How do I enforce a policy on audit_install_drift? +

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.

What risk level is audit_install_drift? +

audit_install_drift is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit audit_install_drift? +

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.

How do I block audit_install_drift completely? +

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.

What MCP server provides audit_install_drift? +

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.

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Samarth Gtm's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.