list_connection_dialects
AI agents call list_connection_dialects 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 'list' verb indicates a query or retrieval operation with no side effects. Listing connection dialects is informational only—it does not create, modify, delete, or execute any operations. The empty description slightly lowers confidence, but the naming convention clearly indicates a read operation. This poses minimal risk as it only returns metadata about supported database types.
From the tool's definition Tool name 'list_connection_dialects' uses the 'list' verb, which is a read-only operation that retrieves available database dialects for connections. No parameters are mentioned that would enable modification or deletion.
Attacks that exploit this kind of access
list_connection_dialects. 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 list_connection_dialects: 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.
list_connection_dialects 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 list_connection_dialects 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 list_connection_dialects. 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.
list_connection_dialects 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 →