AI agents call drop_stored_procedure to permanently remove resources in Mcp Windows — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool performs an irreversible deletion of a stored procedure from a database. Once dropped, the procedure and its definition are permanently removed and cannot be recovered without a backup. This is a destructive operation that cannot be undone. The high severity reflects that an AI agent misusing this could permanently destroy business-critical stored procedures, affecting applications that depend on them.
From the tool's definition Tool name is 'drop_stored_procedure' and description states 'Drop a stored procedure.' The verb 'drop' in database terminology means irreversible deletion of a database object.
Documented attack patterns abuse exactly the kind of access drop_stored_procedure gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Windows, and nothing reaches the server without passing your rules. This is the rule we recommend for drop_stored_procedure:
{
"version": "1",
"default": "deny",
"hide": [
"drop_stored_procedure"
]
}drop_stored_procedure disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Drop a stored procedure. It is categorised as a Destructive tool in the Mcp Windows MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Mcp Windows MCP server in PolicyLayer and add a rule for drop_stored_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 Mcp Windows. Nothing to install.
drop_stored_procedure is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the drop_stored_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 drop_stored_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.
drop_stored_procedure is provided by the Mcp Windows MCP server (mukul975/mcp-windows-automation). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 441 Mcp Windows tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
441 Mcp Windows tools catalogued and risk-classified — across an index of 42,500+ MCP servers.