execute_sql · Databricks MCP Server MCP: Risk & Policy

WHAT IT DOES

What execute_sql does on Databricks MCP Server

AI agents invoke execute_sql to trigger actions in Databricks MCP Server. 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.

WHY IT NEEDS A POLICY

Why execute_sql needs a policy

This tool triggers execution of arbitrary SQL queries against a Databricks warehouse. While SQL can perform read-only queries (SELECT), the tool's purpose is to execute any SQL statement provided as an argument, including those with side effects like INSERT, UPDATE, DELETE, or DDL operations. This makes it an Execute category tool—the effects depend entirely on the SQL statement content provided by the caller.

From the tool's definition Tool is named 'execute_sql' and description explicitly states it 'Execute[s] a SQL statement' with parameters for warehouse_id, catalog, and schema.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

execute_sql Rate-limited

execute_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": {
    "execute_sql": {
      "limits": [
        {
          "counter": "execute_sql_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Databricks MCP Server, so you can run agents against it safely.

FAQ

Questions about execute_sql

What does the execute_sql tool do? +

Execute a SQL statement with parameters: statement (required), warehouse_id (optional - uses DATABRICKS_WAREHOUSE_ID env var if not provided), catalog (optional), schema (optional). It is categorised as a Execute tool in the Databricks MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on execute_sql? +

Register the Databricks MCP Server MCP server in PolicyLayer and add a rule for execute_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 Databricks MCP Server. Nothing to install.

What risk level is execute_sql? +

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

Can I rate-limit execute_sql? +

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

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

execute_sql is provided by the Databricks MCP Server MCP server (robkisk/databricks-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.