delete_view

THE RISK

Critical Risk

Why delete_view needs a policy

Deleting a view is a destructive operation that permanently removes a database object and cannot be undone without restoration from backups. This falls under the Destructive category rather than Write because the action is irreversible.

From the tool's definition Tool name is 'delete_view' with description 'Delete a view'. The verb 'delete' combined with database schema modification indicates irreversible removal of a database object.

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

POLICY

How to control delete_view

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_view:

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_view"
  ]
}

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

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

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More MSSQL MCP Server tools

Destructive delete_index Delete an index Destructive delete_procedure Delete a stored procedure Execute execute_procedure Execute a stored procedure with optional parameters Write create_index Create a new index Write create_procedure Create a new stored procedure Write create_table Create a new table in the database Write create_view Create a new view Write modify_procedure Modify an existing stored procedure

All 23 MSSQL MCP Server tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in MSSQL MCP Server → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about delete_view

What does the delete_view tool do? +

Delete a view. 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_view? +

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

delete_view 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_view? +

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

Set action: deny in the PolicyLayer policy for delete_view. 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_view? +

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

CHECK YOUR STACK →