get_user_attribute
AI agents call get_user_attribute 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.
The tool retrieves user attribute data with no indication of side effects or data modification. Even without a description, the 'get_' prefix combined with 'user_attribute' (a data property rather than an action) strongly suggests a read operation. Confidence is reduced slightly due to missing description, but the pattern is clear enough to classify with reasonable confidence.
From the tool's definition Tool name 'get_user_attribute' indicates retrieval of user attributes without modification capability. No description provided to confirm, but naming convention and sibling tools (which include write/execute operations like create_*, add_*) suggest this is a…
Attacks that exploit this kind of access
get_user_attribute. 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_user_attribute: 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_user_attribute 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_attribute 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_attribute. 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_attribute 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 →