triggers_list

List all GTM triggers in a workspace. Automatically follows pagination to return all triggers.

SERVERSamarth Gtm Mcp SOURCEsamarth-gtm-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-samarthanalytics-sj-samarth-gtm-mcp/triggers-list.md

WHAT IT DOES

What triggers_list does on Samarth Gtm Mcp

AI agents call triggers_list to retrieve information from Samarth Gtm Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why triggers_list is rated Low

This tool queries and retrieves GTM trigger configurations from Google Tag Manager. It performs no mutations, does not execute code or external operations, and does not delete data. The read-only nature is reinforced by the server description stating 'Read-only by default.' Listing triggers is an informational operation with minimal blast radius if misused by an AI agent.

From the tool's definition Tool name contains 'list' and description states 'List all GTM triggers' with automatic pagination—purely retrieves existing data without modification or execution.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs triggers_list safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Samarth Gtm Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For triggers_list, this is the rule to start with:

triggers_list Allowed

triggers_list is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "triggers_list": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Samarth Gtm Mcp, apply this rule, and every triggers_list call is checked against it from then on.

FAQ

Questions about triggers_list

What does the triggers_list tool do? +

List all GTM triggers in a workspace. Automatically follows pagination to return all triggers. It is categorised as a Read tool in the Samarth Gtm Mcp MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on triggers_list? +

Register the Samarth Gtm MCP server in PolicyLayer and add a rule for triggers_list: 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 Samarth Gtm Mcp. Nothing to install.

What risk level is triggers_list? +

triggers_list is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit triggers_list? +

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

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

triggers_list is provided by the Samarth Gtm MCP server (samarth-gtm-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Samarth Gtm, and thousands of servers like it.

This server

All 236 Samarth Gtm tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_circuits on 0gzk →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →