validate_sql

Check SQL query for syntax issues and security concerns

SERVERMetabase MCP SOURCE1luvc0d3/metabase-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What validate_sql does on Metabase MCP

AI agents call validate_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.

RISK

Why validate_sql is rated Low

This tool performs static analysis of SQL queries (syntax validation and security scanning) without executing them against any database. It reads and inspects input but produces no side effects on data, infrastructure, or external systems.

From the tool's definition Tool name is 'validate_sql' and description states it 'Check SQL query for syntax issues and security concerns' — the word 'check' and 'validate' indicate inspection/analysis without execution or modification of data or systems.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

validate_sql Allowed

validate_sql is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "validate_sql": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about validate_sql

What does the validate_sql tool do? +

Check SQL query for syntax issues and security concerns. It is categorised as a Read tool in the Metabase MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on validate_sql? +

Register the Metabase MCP server in PolicyLayer and add a rule for validate_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 validate_sql? +

validate_sql is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit validate_sql? +

Yes. Add a rate_limit block to the validate_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 validate_sql completely? +

Set action: deny in the PolicyLayer policy for validate_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 validate_sql? +

validate_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 →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →