list_gtm_variables
List the user-defined variables in a GTM workspace (name + type). Use it to check whether a variable already exists before creating one.
This record as markdown: /tools/io-github-samarthanalytics-sj-samarth-gtm-mcp/list-gtm-variables.md
What list_gtm_variables does on Samarth Gtm Mcp
AI agents call list_gtm_variables 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.
Why list_gtm_variables is rated Low
Tool retrieves variable metadata without side effects; no data modification, deletion, or execution.
From the tool's definition List the user-defined variables in a GTM workspace (name + type).
Attacks that exploit this kind of access
The rule that runs list_gtm_variables 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 list_gtm_variables, this is the rule to start with:
list_gtm_variables is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Samarth Gtm Mcp, apply this rule, and every list_gtm_variables call is checked against it from then on.
Questions about list_gtm_variables
List the user-defined variables in a GTM workspace (name + type). Use it to check whether a variable already exists before creating one. It is categorised as a Read tool in the Samarth Gtm Mcp MCP Server, which means it retrieves data without modifying state.
Register the Samarth Gtm MCP server in PolicyLayer and add a rule for list_gtm_variables: 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.
list_gtm_variables is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_gtm_variables 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 list_gtm_variables. 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.
list_gtm_variables 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.
More on Samarth Gtm, and thousands of servers like it.
This server
Across the catalogue