Performs all destination operations: get, list, link, unlink. The
AI agents use gtm_destination to create or update resources in Unboundai Gtm — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Unboundai Gtm environment.
The tool supports both read operations (get, list) and write/destructive operations (link, unlink). Linking and unlinking destinations in Google Tag Manager can affect tracking configurations across web properties. The most severe applicable category is Write (link/unlink are reversible modifications), though unlinking could have significant operational impact.
From the tool's definition Performs all destination operations: get, list, link, unlink
Attacks that exploit this kind of access
Performs all destination operations: get, list, link, unlink. The. It is categorised as a Write tool in the Unboundai Gtm MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Unboundai Gtm MCP server in PolicyLayer and add a rule for gtm_destination: 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 Unboundai Gtm. Nothing to install.
gtm_destination 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 gtm_destination 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 gtm_destination. 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.
gtm_destination is provided by the Unboundai Gtm MCP server (tijevlam/unboundai-google-tag-manager-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →