Critical Risk →

delete_procedure

Delete a stored procedure

How to control delete_procedure ↓

What delete_procedure does on MSSQL MCP Server

AI agents call delete_procedure to permanently remove resources in MSSQL MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

Why delete_procedure needs a policy

Deleting a stored procedure destroys a database object permanently and cannot be undone. This matches the Destructive category definition: 'irreversibly deletes or overwrites data, or actions that cannot be undone (delete, drop, purge, force-push).' While the blast radius is somewhat constrained by the specificity of targeting a named procedure, the operation is inherently destructive and could disrupt application…

From the tool's definition delete_procedure deletes a stored procedure, an irreversible database object removal operation.

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

How to control delete_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 delete_procedure:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_procedure"
  ]
}

delete_procedure disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

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

Free to start. No card required.

Related tools and policies

Go deeper

Questions about delete_procedure

What does the delete_procedure tool do? +

Delete a stored procedure. It is categorised as a Destructive tool in the MSSQL MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on delete_procedure? +

Register the MSSQL MCP Server MCP server in PolicyLayer and add a rule for delete_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 delete_procedure? +

delete_procedure is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete_procedure? +

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

Set action: deny in the PolicyLayer policy for delete_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 delete_procedure? +

delete_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.

Free to start. No card required.

23 MSSQL MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.