Execute a stored procedure with parameters (requires MSSQL_ALLOW_WRITE_OPERATIONS=true).
AI agents invoke mssql_execute_procedure to trigger actions in MSSQL Database 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.
Stored procedures are executable code artifacts that can perform any operation supported by SQL Server, including reads, writes, deletes, or calls to extended stored procedures that interact with the operating system.
From the tool's definition Tool name contains 'execute_procedure' and description states it 'Execute[s] a stored procedure with parameters'.
Attacks that exploit this kind of access
Execute a stored procedure with parameters (requires MSSQL_ALLOW_WRITE_OPERATIONS=true). It is categorised as a Execute tool in the MSSQL Database MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the MSSQL Database MCP Server MCP server in PolicyLayer and add a rule for mssql_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 Database MCP Server. Nothing to install.
mssql_execute_procedure is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the mssql_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.
Set action: deny in the PolicyLayer policy for mssql_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.
mssql_execute_procedure is provided by the MSSQL Database MCP Server MCP server (vpro1032/mssql-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →