execute_dbsql · Databricks MCP Server MCP: Risk & Policy

WHAT IT DOES

What execute_dbsql does on Databricks MCP Server

AI agents invoke execute_dbsql 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_dbsql needs a policy

The tool executes SQL queries against Databricks, which can perform data modifications, retrieve sensitive information, or trigger external operations depending on the query content. This is Execute rather than Write because the impact is determined by argument content (the SQL query itself), and SQL execution can include destructive operations.

From the tool's definition Tool name 'execute_dbsql' indicates execution of Databricks SQL queries. Context states server supports 'SQL execution' via Databricks SDK. Tool description is empty, but the name and server capabilities clearly indicate arbitrary SQL execution.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

execute_dbsql Rate-limited

execute_dbsql 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_dbsql": {
      "limits": [
        {
          "counter": "execute_dbsql_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_dbsql

What does the execute_dbsql tool do? +

execute_dbsql. 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_dbsql? +

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

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

Can I rate-limit execute_dbsql? +

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

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

execute_dbsql is provided by the Databricks MCP Server MCP server (not4yazwz/databricks_custom_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.