execute_sql_nonblocking · Databricks MCP Server MCP

WHAT IT DOES

What execute_sql_nonblocking does on Databricks MCP Server

AI agents invoke execute_sql_nonblocking 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_nonblocking needs a policy

This tool executes arbitrary SQL statements against a Databricks instance. SQL execution is fundamentally an Execute action because it runs code (SQL) on external infrastructure with side effects that vary by statement content.

From the tool's definition Tool description explicitly states 'Start SQL statement execution', which triggers external database operations whose effects depend on the SQL statement content provided as arguments.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

execute_sql_nonblocking Rate-limited

execute_sql_nonblocking 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_nonblocking": {
      "limits": [
        {
          "counter": "execute_sql_nonblocking_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_nonblocking

What does the execute_sql_nonblocking tool do? +

Start SQL statement execution and return immediately with statement_id (non-blocking). 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_nonblocking? +

Register the Databricks MCP Server MCP server in PolicyLayer and add a rule for execute_sql_nonblocking: 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_nonblocking? +

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

Can I rate-limit execute_sql_nonblocking? +

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

Set action: deny in the PolicyLayer policy for execute_sql_nonblocking. 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_nonblocking? +

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