execute_query_write · MSSQL MCP Server MCP: Risk & Policy

WHAT IT DOES

What execute_query_write does on MSSQL MCP Server

AI agents invoke execute_query_write to trigger actions in MSSQL 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_query_write needs a policy

This tool executes write operations (INSERT, UPDATE, DELETE) against a live database. While it validates query safety and supports transaction control (allowing rollback), it can still modify or delete data at scale. DELETE operations make this more severe than a simple Write.

From the tool's definition 'Execute a write query (INSERT, UPDATE, DELETE) against the database' and 'Validates query safety before execution'

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

execute_query_write Rate-limited

execute_query_write 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_query_write": {
      "limits": [
        {
          "counter": "execute_query_write_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 MSSQL MCP Server, so you can run agents against it safely.

FAQ

Questions about execute_query_write

What does the execute_query_write tool do? +

Execute a write query (INSERT, UPDATE, DELETE) against the database. Can be part of a transaction or auto-committed. Validates query safety before execution. It is categorised as a Execute tool in the MSSQL 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_query_write? +

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

What risk level is execute_query_write? +

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

Can I rate-limit execute_query_write? +

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

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

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