sql_run_script · MCP SQL Server MCP: Risk & Policy

WHAT IT DOES

What sql_run_script does on MCP SQL Server

AI agents invoke sql_run_script to trigger actions in MCP SQL 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 sql_run_script needs a policy

This tool executes SQL code with side effects determined by user input. Although the sibling tool 'sql_run' also exists (suggesting some queries are intentionally allowed), 'sql_run_script' explicitly executes multiple statements in sequence, which is characteristic of Execute category—code execution with blast radius depending on the SQL provided.

From the tool's definition Tool description states 'Ejecuta múltiples sentencias SQL en secuencia' (Executes multiple SQL statements in sequence). The name 'sql_run_script' and capability to execute arbitrary SQL statements sequentially indicates code execution.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

sql_run_script Rate-limited

sql_run_script 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": {
    "sql_run_script": {
      "limits": [
        {
          "counter": "sql_run_script_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 MCP SQL Server, so you can run agents against it safely.

FAQ

Questions about sql_run_script

What does the sql_run_script tool do? +

Ejecuta múltiples sentencias SQL en secuencia; se detiene al primer error. It is categorised as a Execute tool in the MCP SQL 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 sql_run_script? +

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

What risk level is sql_run_script? +

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

Can I rate-limit sql_run_script? +

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

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

sql_run_script is provided by the MCP SQL Server MCP server (miguel1603/mcp-sql). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.