execute_procedure

THE RISK

High Risk

Why execute_procedure needs a policy

Stored procedures can contain any SQL operations (SELECT, INSERT, UPDATE, DELETE, DDL, or administrative commands). The tool accepts optional parameters that could be manipulated to alter procedure behavior. Execution effects are dependent on procedure implementation and arguments, making this an Execute category risk.

From the tool's definition Tool name 'execute_procedure' combined with description 'Execute a stored procedure with optional parameters' indicates dynamic execution of arbitrary stored procedures.

Documented attack patterns abuse exactly the kind of access execute_procedure gives an agent:

POLICY

How to control execute_procedure

PolicyLayer is an MCP gateway — it sits between your AI agents and MSSQL MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for execute_procedure:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "execute_procedure": {
      "limits": [
        {
          "counter": "execute_procedure_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

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.

Create a free account and register MSSQL MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RATE-LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More MSSQL MCP Server tools

Destructive delete_index Delete an index Destructive delete_procedure Delete a stored procedure Destructive delete_view Delete a view Write create_index Create a new index Write create_procedure Create a new stored procedure Write create_table Create a new table in the database Write create_view Create a new view Write modify_procedure Modify an existing stored procedure

All 23 MSSQL MCP Server tools →

Execute tools on other servers

Android Forensics ADB MCP Server adb_shell_command EMBA-MCP run_emba_scan Frida Game Hacking MCP remove_breakpoint Procmon request_elevation

Go deeper

High-risk tools in MSSQL MCP Server → Every high-risk tool this server exposes, in one view.
All high-risk MCP tools → Every high-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Agent sandbox → Bounding what an agent can execute and where the boundary should sit.
Least privilege for MCP → Granting agents the minimum tool surface the task needs.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about execute_procedure

What does the execute_procedure tool do? +

Execute a stored procedure with optional parameters. 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_procedure? +

Register the MSSQL MCP Server 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 MSSQL MCP Server. 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 MSSQL MCP Server MCP server (jensenloke/mcp-sqlserver-pro). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every MSSQL MCP Server tool call.

Start from MSSQL MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →