create_complete_ecommerce_setup

WHAT IT DOES

What create_complete_ecommerce_setup does on Google Tag Manager MCP Server

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

WHY IT NEEDS A POLICY

Why create_complete_ecommerce_setup needs a policy

This tool creates GTM configurations (tags, triggers, variables) that are persisted in the live GTM account. While it does not delete data (so not Destructive) or execute arbitrary code on user systems (so not Execute in the dangerous sense), it does modify the target GTM account's state by adding new tracking elements. This is a Write operation because it creates reversible configurations.

From the tool's definition Tool description states 'Create complete ecommerce tracking setup in GTM' with Korean text '(실제 GTM에 생성)' meaning '(actually created in GTM)', indicating it creates and persists tracking configurations in the actual Google Tag Manager account.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_complete_ecommerce_setup Rate-limited

create_complete_ecommerce_setup 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": {
    "create_complete_ecommerce_setup": {
      "limits": [
        {
          "counter": "create_complete_ecommerce_setup_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Google Tag Manager MCP Server, so you can run agents against it safely.

FAQ

Questions about create_complete_ecommerce_setup

What does the create_complete_ecommerce_setup tool do? +

Create complete ecommerce tracking setup in GTM (실제 GTM에 생성). 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.

How do I enforce a policy on create_complete_ecommerce_setup? +

Register the Google Tag Manager MCP Server MCP server in PolicyLayer and add a rule for create_complete_ecommerce_setup: 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.

What risk level is create_complete_ecommerce_setup? +

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

Can I rate-limit create_complete_ecommerce_setup? +

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

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

create_complete_ecommerce_setup is provided by the Google Tag Manager MCP Server MCP server (neep305/mcp-for-gtm). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.