nlq_to_sql

Convert a natural language question to SQL query

SERVERMetabase MCP SOURCE1luvc0d3/metabase-mcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/1luvc0d3-metabase-mcp/nlq-to-sql.md

WHAT IT DOES

What nlq_to_sql does on Metabase MCP

AI agents invoke nlq_to_sql to trigger actions in Metabase MCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

RISK

Why nlq_to_sql is rated High

Converting NLP to SQL and running it constitutes code execution with unpredictable scope. Depending on the underlying DB permissions, generated SQL could include SELECT (Read), INSERT/UPDATE (Write), or even DROP/DELETE (Destructive). The natural language interface makes it impossible to statically bound the operation, and the sibling 'batch_execute' and 'execute_card' tools suggest this server runs queries actively.

From the tool's definition 'Convert a natural language question to SQL query' — the tool generates and likely executes SQL from arbitrary natural language input

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs nlq_to_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 nlq_to_sql, this is the rule to start with:

nlq_to_sql Rate-limited

nlq_to_sql stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "nlq_to_sql": {
      "limits": [
        {
          "counter": "nlq_to_sql_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Metabase MCP, apply this rule, and every nlq_to_sql call is checked against it from then on.

FAQ

Questions about nlq_to_sql

What does the nlq_to_sql tool do? +

Convert a natural language question to SQL query. It is categorised as a Execute tool in the Metabase MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on nlq_to_sql? +

Register the Metabase MCP server in PolicyLayer and add a rule for nlq_to_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.

What risk level is nlq_to_sql? +

nlq_to_sql is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit nlq_to_sql? +

Yes. Add a rate_limit block to the nlq_to_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.

How do I block nlq_to_sql completely? +

Set action: deny in the PolicyLayer policy for nlq_to_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.

What MCP server provides nlq_to_sql? +

nlq_to_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.

KEEP EXPLORING

More on Metabase, and thousands of servers like it.

This server

All 30 Metabase tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →