execute_procedure · SQL Server MCP Service MCP

WHAT IT DOES

What execute_procedure does on SQL Server MCP Service

AI agents invoke execute_procedure to trigger actions in SQL Server MCP Service. 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_procedure needs a policy

Stored procedures can perform arbitrary operations—reads, writes, deletes, or even financial transactions—depending on their implementation. The tool's ability to execute parameterized procedures makes it an Execute risk rather than Read (it triggers external operations) or Destructive (the server claims protection against destructive operations, and the actual impact depends on procedure design).

From the tool's definition Tool name 'execute_procedure' and description 'Executes a stored procedure with parameters' indicate the tool runs code (a stored procedure) whose effects depend on the procedure logic and arguments passed.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

execute_procedure Rate-limited

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

FAQ

Questions about execute_procedure

What does the execute_procedure tool do? +

Executes a stored procedure with parameters. It is categorised as a Execute tool in the SQL Server MCP Service 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_procedure? +

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

What risk level is execute_procedure? +

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

Can I rate-limit execute_procedure? +

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

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

execute_procedure is provided by the SQL Server MCP Service MCP server (vini-cius/mcp-sqlserver). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.