This record as markdown: /tools/1luvc0d3-metabase-mcp/explain-sql.md
What explain_sql does on Metabase MCP
AI agents call explain_sql to retrieve information from Metabase MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why explain_sql is rated Low
This tool performs query analysis and explanation only—a retrieval and informational operation. It does not execute SQL, modify data, or trigger side effects. The worst-case misuse would be explaining sensitive queries to reveal their structure, but this is a read-only information disclosure risk rather than a data manipulation or execution risk. Severity is low because explanation alone cannot alter system state.
From the tool's definition Tool name 'explain_sql' and description 'Explain a SQL query in plain English' indicates this tool analyzes and describes existing SQL queries without executing them or modifying any data.
Attacks that exploit this kind of access
The rule that runs explain_sql safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Metabase MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For explain_sql, this is the rule to start with:
explain_sql is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Metabase MCP, apply this rule, and every explain_sql call is checked against it from then on.
Questions about explain_sql
Explain a SQL query in plain English. It is categorised as a Read tool in the Metabase MCP MCP Server, which means it retrieves data without modifying state.
Register the Metabase MCP server in PolicyLayer and add a rule for explain_sql: 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 Metabase MCP. Nothing to install.
explain_sql 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 explain_sql 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 explain_sql. 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.
explain_sql is provided by the Metabase MCP server (1luvc0d3/metabase-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Metabase, and thousands of servers like it.
This server
Across the catalogue