Permanently and irreversibly delete a table. This cannot be undone. The table must already be in the trash (deleted with delete_table first).
AI agents call permanently_delete_table 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.
This tool permanently removes a table from a Teable database with no recovery option. The description emphasizes the irreversible nature ('cannot be undone'), which is the defining characteristic of the Destructive category. The critical severity reflects that an AI agent misusing this could cause permanent loss of entire datasets and business data.
From the tool's definition Tool name contains 'permanently_delete' and description explicitly states 'Permanently and irreversibly delete a table. This cannot be undone.' These phrases directly indicate irreversible data destruction.
Documented attack patterns abuse exactly the kind of access permanently_delete_table gives an agent:
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 permanently_delete_table:
{
"version": "1",
"default": "deny",
"hide": [
"permanently_delete_table"
]
} permanently_delete_table 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.
Permanently and irreversibly delete a table. This cannot be undone. The table must already be in the trash (deleted with delete_table first). 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.
Register the Teable MCP Server MCP server in PolicyLayer and add a rule for permanently_delete_table: 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.
permanently_delete_table 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 permanently_delete_table 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 permanently_delete_table. 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.
permanently_delete_table 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.
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.