Manages GTM folders for organizing tags, triggers, and variables.
AI agents use gtm_folder to create or update resources in Google Tag Manager MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Google Tag Manager MCP Server environment.
The tool manages GTM folders, implying it can create, update, or delete organizational folder structures within Google Tag Manager. 'Manages' suggests write-level operations (create/update/rename) as the primary use case.
From the tool's definition 'Manages GTM folders for organizing tags, triggers, and variables'
Attacks that exploit this kind of access
Manages GTM folders for organizing tags, triggers, and variables. It is categorised as a Write tool in the Google Tag Manager MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Google Tag Manager MCP Server MCP server in PolicyLayer and add a rule for gtm_folder: 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 Google Tag Manager MCP Server. Nothing to install.
gtm_folder 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_folder 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_folder. 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_folder is provided by the Google Tag Manager MCP Server MCP server (metkamedia/gtm-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 →