execute_sql

Run a SQL statement against selected database.

SERVERMulti-DB MCP Server SOURCE1249zts/db-mcp-service

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade C, identity unverified Pull the record →

This record as markdown: /tools/1249zts-db-mcp-service/execute-sql.md

WHAT IT DOES

What execute_sql does on Multi-DB MCP Server

AI agents invoke execute_sql to trigger actions in Multi-DB 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.

RISK

Why execute_sql is rated High

While the tool's primary purpose appears to be query execution (Read), the capability to 'run a SQL statement' without specification of statement type means it can execute destructive operations (DELETE, DROP TABLE, TRUNCATE), data modifications (INSERT, UPDATE), and administrative commands depending on user/agent input.

From the tool's definition Tool name 'execute_sql' combined with description 'Run a SQL statement against selected database' indicates arbitrary SQL execution capability.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs execute_sql safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Multi-DB MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For execute_sql, this is the rule to start with:

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.

The button opens the PolicyLayer dashboard: create your workspace, connect Multi-DB MCP Server, apply this rule, and every execute_sql call is checked against it from then on.

FAQ

Questions about execute_sql

What does the execute_sql tool do? +

Run a SQL statement against selected database. It is categorised as a Execute tool in the Multi-DB 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 Multi-DB 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 Multi-DB 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 Multi-DB MCP Server MCP server (1249zts/db-mcp-service). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Multi-DB MCP Server, and thousands of servers like it.

This server

All 5 Multi-DB MCP Server tools → High-risk tools on this server →

Across the catalogue

claude_execute on Claude Bridge →execute_test_case on Percepta MCP Server → All high-risk MCP tools → The MCP Attack Database →

Guides

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