delete_record

THE RISK

Critical Risk

Why delete_record needs a policy

delete_record removes data permanently without recovery option. This is irreversible data loss, placing it in the Destructive category. Severity is high (not critical) because the blast radius is limited to a single record; however, in a production database, even deleting one record could have significant downstream consequences depending on context.

From the tool's definition Tool description explicitly states 'Permanently delete a record (all data will be lost). This operation is irreversible.' The word 'Permanently' and 'irreversible' directly confirm destructive intent.

Risk signalsBulk/mass operation — affects multiple targets

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

POLICY

How to control delete_record

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

policy.json

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

delete_record 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 Teable 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 Teable MCP Server tools

Destructive delete_field Permanently delete a field from a table (all data in this field will be lost) Destructive delete_table Delete a table (moves to trash, recoverable via restore_table_from_trash) Destructive delete_view Delete a view from a table Destructive permanently_delete_table Permanently and irreversibly delete a table. This cannot be undone. The table must already Write share_view Enable or disable public share link for a view. Returns the share URL when enabled. Write comment_on_record Post a comment on a specific record Write create_field Create a new field in a table Write create_record Create a new record in a table

All 29 Teable 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 Teable 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_record

What does the delete_record tool do? +

Permanently delete a record (all data will be lost). This operation is irreversible. 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_record? +

Register the Teable MCP Server MCP server in PolicyLayer and add a rule for delete_record: 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_record? +

delete_record 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_record? +

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

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

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

CHECK YOUR STACK →