AI agents use modify_procedure to create or update resources in MSSQL MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MSSQL MCP Server environment.
This tool modifies an existing stored procedure in the database. While it alters database objects, it is reversible (the procedure can be modified again or dropped). However, since stored procedures can contain arbitrary SQL logic including destructive operations, misuse carries high blast radius—an AI agent could alter business-critical procedures to behave maliciously or incorrectly.
From the tool's definition "Modify an existing stored procedure"
Documented attack patterns abuse exactly the kind of access modify_procedure gives an agent:
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 modify_procedure:
{
"version": "1",
"default": "deny",
"tools": {
"modify_procedure": {
"limits": [
{
"counter": "modify_procedure_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}modify_procedure stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Modify an existing stored procedure. It is categorised as a Write tool in the MSSQL MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MSSQL MCP Server MCP server in PolicyLayer and add a rule for modify_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.
modify_procedure is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the modify_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 modify_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.
modify_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.
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.
Free to start. No card required.
23 MSSQL MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.