get_user_permissions
AI agents call get_user_permissions to retrieve information from Mcp Read Only Grafana without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'get_' prefix and context of a read-only Grafana server indicate this tool retrieves and queries permission data without modification. Retrieving user permissions is a non-destructive read operation with minimal blast radius if misused—it may expose sensitive permission structures but does not execute code, modify data, delete resources, or move money.
From the tool's definition Tool name 'get_user_permissions' with 'get' verb indicates data retrieval. Server description states 'provides read-only access by default', and this tool appears to be a read operation that retrieves user permission information.
Attacks that exploit this kind of access
get_user_permissions. It is categorised as a Read tool in the Mcp Read Only Grafana MCP Server, which means it retrieves data without modifying state.
Register the Mcp Read Only Grafana MCP server in PolicyLayer and add a rule for get_user_permissions: 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 Mcp Read Only Grafana. Nothing to install.
get_user_permissions 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 get_user_permissions 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 get_user_permissions. 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.
get_user_permissions is provided by the Mcp Read Only Grafana MCP server (lukleh/mcp-read-only-grafana). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →