get_credentials_email
AI agents call get_credentials_email 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 (does not modify or delete) credentials, placing it in Read category. However, severity is elevated to high because credentials are sensitive security material—unauthorized retrieval could enable account takeover or unauthorized access to Looker and connected systems. Confidence is moderate (0.60) due to the empty description; a fuller description of scope (user's own credentials vs.
From the tool's definition Tool name 'get_credentials_email' indicates retrieval of email credentials; description is empty. Context from sibling tools (create_credentials_email, create_credentials_api3) suggests this retrieves stored authentication material.
Attacks that exploit this kind of access
get_credentials_email. 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_credentials_email: 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_credentials_email 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_credentials_email 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_credentials_email. 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_credentials_email 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 →