delete_mssql_database
Delete MSSQL database (DESTRUCTIVE)
This record as markdown: /tools/cbrown35-20i-mcp/delete-mssql-database.md
What delete_mssql_database does on 20i MCP Server
AI agents call delete_mssql_database to permanently remove resources in 20i MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why delete_mssql_database is rated Critical
Deleting a database is a destructive operation that cannot be undone—data is permanently lost. This has the highest blast radius if triggered by an AI agent without proper authorization or context, potentially causing significant data loss and service disruption for hosted applications. The critical severity reflects the permanent nature of the action and its impact on customer data and business continuity.
From the tool's definition Tool name explicitly states 'delete_mssql_database' and description includes '(DESTRUCTIVE)' label. This operation removes data irreversibly without recovery options.
Attacks that exploit this kind of access
The rule that runs delete_mssql_database safely
PolicyLayer is an MCP gateway: it sits between your AI agents and 20i MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_mssql_database, this is the rule to start with:
delete_mssql_database is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect 20i MCP Server, apply this rule, and every delete_mssql_database call is checked against it from then on.
Questions about delete_mssql_database
Delete MSSQL database (DESTRUCTIVE). It is categorised as a Destructive tool in the 20i MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the 20i MCP Server MCP server in PolicyLayer and add a rule for delete_mssql_database: 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 20i MCP Server. Nothing to install.
delete_mssql_database 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 delete_mssql_database 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 delete_mssql_database. 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.
delete_mssql_database is provided by the 20i MCP Server MCP server (cbrown35/20i-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on 20i MCP Server, and thousands of servers like it.
Across the catalogue