variables_list
List all user-defined GTM variables in a workspace. Automatically follows pagination to return all variables.
This record as markdown: /tools/io-github-samarthanalytics-sj-samarth-gtm-mcp/variables-list.md
What variables_list does on Samarth Gtm Mcp
AI agents call variables_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.
Why variables_list is rated Low
This tool queries and retrieves GTM variable metadata without modifying, executing, or deleting anything. It is a straightforward read operation that returns configuration information. The blast radius of misuse is minimal—an agent could enumerate variables but cannot alter GTM setup or trigger tracking changes. The read-only nature of the server architecture further supports the low severity classification.
From the tool's definition Tool description states 'List all user-defined GTM variables in a workspace' with pagination support. The verb 'list' and the server description emphasizing 'read-only by default' confirm this is a data retrieval operation with no side effects.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs variables_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 variables_list, this is the rule to start with:
variables_list 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 variables_list call is checked against it from then on.
Questions about variables_list
List all user-defined GTM variables in a workspace. Automatically follows pagination to return all variables. 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 variables_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.
variables_list 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 variables_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.
Set action: deny in the PolicyLayer policy for variables_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.
variables_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.
More on Samarth Gtm, and thousands of servers like it.
This server
Across the catalogue