built_in_variables_enable

[WRITE] Enable one or more built-in variables in a GTM workspace.

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/built-in-variables-enable.md

WHAT IT DOES

What built_in_variables_enable does on Samarth Gtm Mcp

AI agents use built_in_variables_enable 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.

RISK

Why built_in_variables_enable is rated Medium

This tool modifies GTM workspace configuration by enabling built-in variables, which is a reversible operation (variables can be disabled). It does not delete data, execute arbitrary code, move money, or cause permanent damage. The severity is medium because enabling variables could affect tracking behavior or expose data collection mechanisms, but the change is non-destructive and can be reversed.

From the tool's definition Tool description explicitly marks this as [WRITE] and states it 'Enable[s] one or more built-in variables in a GTM workspace,' which creates or modifies configuration state in Google Tag Manager.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

built_in_variables_enable Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "built_in_variables_enable": {
      "limits": [
        {
          "counter": "built_in_variables_enable_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT 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 built_in_variables_enable call is checked against it from then on.

FAQ

Questions about built_in_variables_enable

What does the built_in_variables_enable tool do? +

[WRITE] Enable one or more built-in variables in a GTM workspace. 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 built_in_variables_enable? +

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

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

Can I rate-limit built_in_variables_enable? +

Yes. Add a rate_limit block to the built_in_variables_enable 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 built_in_variables_enable completely? +

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

built_in_variables_enable 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

Govern customer-ops agents →Argument validation →Scoped token →