Deploy a tested draft to production. This backs up the current version automatically and can be rolled back.
AI agents invoke deploy_sp 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.
deploy_sp triggers execution of code changes in a production environment. Although rollback is available (making it technically reversible), deployment is an Execute action because it runs external operations (stored procedure activation in production) whose effects depend on the procedure being deployed.
From the tool's definition Tool description states 'Deploy a tested draft to production' — this executes a stored procedure deployment that modifies production database code.
Attacks that exploit this kind of access
Deploy a tested draft to production. This backs up the current version automatically and can be rolled back. 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.
Register the MSSQL MCP Server MCP server in PolicyLayer and add a rule for deploy_sp: 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.
deploy_sp 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 deploy_sp 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 deploy_sp. 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.
deploy_sp 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.
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 →