Unboundai Gtm

18 tools. 17 can modify or destroy data without limits.

14 destructive tools with no built-in limits. Policy required.

Last updated:

17 can modify or destroy data
1 read-only
18 tools total

Community server · catalogue entry verified 02/07/2026

How to control Unboundai Gtm ↓

What Unboundai Gtm exposes to your agents

Read (1) Write / Execute (3) Destructive / Financial (14)
Critical Risk

The most dangerous Unboundai Gtm tools

17 of Unboundai Gtm's 18 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

How to control Unboundai Gtm

PolicyLayer is an MCP gateway — it sits between your AI agents and Unboundai Gtm, and nothing reaches the server without passing your rules. These are the rules we recommend:

Deny destructive operations
{
  "gtm_built_in_variable": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations
{
  "gtm_account": {
    "limits": [
      {
        "counter": "gtm_account_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations
{
  "gtm_version_header": {
    "limits": [
      {
        "counter": "gtm_version_header_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

  1. Create a free account and register Unboundai Gtm — nothing to install.
  2. Add these rules — paste them, or build them visually. Tune the limits to your setup.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
ENFORCE POLICY ON UNBOUNDAI GTM →

Instant setup, no code required.

All 18 Unboundai Gtm tools

DESTRUCTIVE 14 tools
Destructive gtm_built_in_variable Performs all built-in variable operations: create, list, remove, revert. The Destructive gtm_client Performs all client operations: create, get, list, update, remove, revert. The Destructive gtm_container Performs all container-related operations: create, get, update, remove, list, combine, lookup, moveTagId, snip Destructive gtm_environment Performs all environment operations: create, get, list, update, remove, reauthorize. The Destructive gtm_folder Performs all folder operations: create, get, list, update, remove, revert, entities, moveEntitiesToFolder. The Destructive gtm_gtag_config Performs all Google tag config operations: create, get, list, update, remove. The Destructive gtm_tag Performs all GTM tag operations: create, get, list, update, remove, revert. The Destructive gtm_template Performs all GTM custom template operations: create, get, list, update, remove, revert. The Destructive gtm_transformation Performs all GTM transformation operations: create, get, list, update, remove, revert. The Destructive gtm_user_permission Performs all user permission operations: create, get, list, update, remove. The Destructive gtm_variable Performs all GTM variable operations: create, get, list, update, remove, revert. The Destructive gtm_version Performs all container version operations: get, live, publish, remove, setLatest, undelete, update. For Destructive gtm_workspace Performs various workspace operations including create, get, list, update, remove, createVersion, getStatus, s Destructive gtm_zone Performs various zone operations including create, get, list, update, remove, and revert actions. The

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

Questions about Unboundai Gtm

Can an AI agent delete data through the Unboundai Gtm MCP server? +

Yes. The Unboundai Gtm server exposes 14 destructive tools including gtm_built_in_variable, gtm_client, gtm_container. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through Unboundai Gtm? +

The Unboundai Gtm server has 2 write tools including gtm_account, gtm_destination. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Unboundai Gtm.

How many tools does the Unboundai Gtm MCP server expose? +

18 tools across 4 categories: Destructive, Execute, Read, Write. 1 are read-only. 17 can modify, create, or delete data.

How do I enforce a policy on Unboundai Gtm? +

Register the Unboundai Gtm MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Unboundai Gtm tool call.

Deterministic rules across all 18 Unboundai Gtm tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Instant setup, no code required.

18 Unboundai Gtm tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.