Get detailed information about a specific role.
AI agents call get_role to retrieve information from Looker MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves role metadata and configuration details from Looker's administrative system. While it is a Read operation (no mutations), the medium severity reflects that role details often include permission grants and access control policies. An agent retrieving comprehensive role information could learn sensitive authorization patterns or identify privileged roles to target in a follow-up attack.
From the tool's definition Tool name is 'get_role' and description states 'Get detailed information about a specific role' — a data retrieval operation with no side effects.
Attacks that exploit this kind of access
Get detailed information about a specific role. It is categorised as a Read tool in the Looker MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Looker MCP Server MCP server in PolicyLayer and add a rule for get_role: 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 Looker MCP Server. Nothing to install.
get_role 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_role 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_role. 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_role is provided by the Looker MCP Server MCP server (ultrathink-solutions/looker-mcp-server). 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 →