AI agents use gtm_create_trigger to create or update resources in Gtm — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Gtm environment.
This tool creates a new trigger, which is a reversible modification to GTM container configuration. While triggers control tag firing and can have broad effects on marketing data collection and site behavior, the action itself is not irreversible (triggers can be deleted or modified).
From the tool's definition Tool name 'gtm_create_trigger' and description 'Create a new trigger in a GTM container' explicitly indicate creation of data within GTM.
Attacks that exploit this kind of access
Create a new trigger in a GTM container. For Custom Event triggers, use custom_event_name parameter for simplified creation. It is categorised as a Write tool in the Gtm MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Gtm MCP server in PolicyLayer and add a rule for gtm_create_trigger: 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 Gtm. Nothing to install.
gtm_create_trigger 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_create_trigger 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_create_trigger. 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_create_trigger is provided by the Gtm MCP server (tijevlam/gtm-mcp). 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 →