AI agents call delete_record to permanently remove resources in Airtable MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes data from an Airtable table with no undo mechanism described. Deletion is irreversible and meets the Destructive category definition. Severity is high because malicious or errant use could destroy important business data, though impact is somewhat bounded to individual records (not critical unless bulk deletion is possible, which appears handled by separate batch_delete_records tool).
From the tool's definition Tool name: 'delete_record'. Tool description: 'Delete a record from a table'. The word 'Delete' combined with the irreversible nature of removing a database record.
Documented attack patterns abuse exactly the kind of access delete_record gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Airtable MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_record:
{
"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.
Free to start. No card required.
Delete a record from a table. It is categorised as a Destructive tool in the Airtable MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Airtable 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 Airtable MCP. Nothing to install.
delete_record 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_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.
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.
delete_record is provided by the Airtable MCP server (rashidazarang/airtable-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 45 Airtable MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
45 Airtable MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.