user_permissions_get
Get a specific user permission record for a GTM account.
This record as markdown: /tools/io-github-samarthanalytics-sj-samarth-gtm-mcp/user-permissions-get.md
What user_permissions_get does on Samarth Gtm Mcp
AI agents call user_permissions_get 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_get is rated Low
This tool queries and retrieves an existing user permission record from GTM. It does not create, modify, delete, or execute any actions. The blast radius of misuse is minimal — an AI agent could view permission metadata but cannot alter access controls or perform unauthorized operations. Aligns with the Read category definition: 'retrieves or queries data; no side effects'.
From the tool's definition Tool name contains 'get' and description states 'Get a specific user permission record' — retrieves data without modification or side effects. Server is described as 'read-only by default' with 'gated writes', confirming this is a read operation.
Attacks that exploit this kind of access
The rule that runs user_permissions_get 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_get, this is the rule to start with:
user_permissions_get 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_get call is checked against it from then on.
Questions about user_permissions_get
Get a specific user permission record for a GTM account. 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_get: 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_get 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_get 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_get. 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_get 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