setup_consent_mode_defaults
Install the Consent Mode v2 DEFAULT-consent tag in a WEB container: a Custom HTML gtag(
This record as markdown: /tools/io-github-samarthanalytics-sj-samarth-gtm-mcp/setup-consent-mode-defaults.md
What setup_consent_mode_defaults does on Samarth Gtm Mcp
AI agents use setup_consent_mode_defaults 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 setup_consent_mode_defaults is rated Medium
This tool creates or modifies tag configurations within GTM containers, which is a reversible write operation. While it affects tracking and consent configuration (potentially sensitive), it does not delete data, execute arbitrary code, or move money. The 'gated writes' and 'audits' mentioned in the server description suggest administrative controls are in place.
From the tool's definition The tool description states 'Install the Consent Mode v2 DEFAULT-consent tag in a WEB container', which indicates creation/modification of a tag configuration in Google Tag Manager.
Attacks that exploit this kind of access
The rule that runs setup_consent_mode_defaults 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 setup_consent_mode_defaults, this is the rule to start with:
setup_consent_mode_defaults 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 setup_consent_mode_defaults call is checked against it from then on.
Questions about setup_consent_mode_defaults
Install the Consent Mode v2 DEFAULT-consent tag in a WEB container: a Custom HTML gtag(. 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 setup_consent_mode_defaults: 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.
setup_consent_mode_defaults 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 setup_consent_mode_defaults 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 setup_consent_mode_defaults. 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.
setup_consent_mode_defaults 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