user_permissions_list
List all user permissions for a GTM account. Automatically follows pagination.
This record as markdown: /tools/io-github-samarthanalytics-sj-samarth-gtm-mcp/user-permissions-list.md
What user_permissions_list does on Samarth Gtm Mcp
AI agents call user_permissions_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 user_permissions_list is rated Low
This tool retrieves and lists existing user permissions without modifying, executing, or destructing any data. It is a straightforward read operation that has no side effects beyond data retrieval. The low severity reflects that while it exposes access control information, it is informational only and does not enable unauthorized actions by itself.
From the tool's definition Tool name 'user_permissions_list' and description 'List all user permissions for a GTM account' indicate a retrieval operation with no data modification. The verb 'List' and context of 'read-only by default' server confirm this is a query operation.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs user_permissions_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 user_permissions_list, this is the rule to start with:
user_permissions_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 user_permissions_list call is checked against it from then on.
Questions about user_permissions_list
List all user permissions for a GTM account. Automatically follows pagination. 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 user_permissions_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.
user_permissions_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 user_permissions_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 user_permissions_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.
user_permissions_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