Critical Risk →

delete_view

Delete a view from a table

How to control delete_view ↓

What delete_view does on Teable MCP Server

AI agents call delete_view to permanently remove resources in Teable 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_view needs a policy

Deletion of views cannot be undone and permanently removes user-created view definitions, layouts, and associated settings. While not as severe as deleting entire tables or records, it represents irreversible data loss of view metadata. This is categorized as Destructive rather than Write because the operation is one-way and cannot be recovered through normal means.

From the tool's definition Tool name is 'delete_view' and description states 'Delete a view from a table' — this is an irreversible deletion operation that removes a saved view configuration.

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

How to control delete_view

PolicyLayer is an MCP gateway — it sits between your AI agents and Teable 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.

  1. Create a free account and register Teable 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_view

What does the delete_view tool do? +

Delete a view from a table. It is categorised as a Destructive tool in the Teable 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 Teable 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 Teable 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 Teable MCP Server MCP server (ltphat2204/teable-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Teable MCP Server tool call.

Start from Teable 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.

29 Teable 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.