Delete multiple records at once (up to 10)
AI agents call batch_delete_records 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.
Deletion is irreversible and cannot be undone. Even though the batch size is limited to 10 records, the tool permanently removes data from Airtable. This is the most severe category applicable, as it destroys data without recovery mechanism. High severity due to potential for bulk data loss if an AI agent misapplies this tool (e.g., deleting wrong records due to prompt injection or misunderstanding of user intent).
From the tool's definition Tool name 'batch_delete_records' explicitly states deletion operation. Description: 'Delete multiple records at once (up to 10)' confirms irreversible removal of data.
Risk signalsBulk/mass operation — affects multiple targets
Documented attack patterns abuse exactly the kind of access batch_delete_records 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 batch_delete_records:
{
"version": "1",
"default": "deny",
"hide": [
"batch_delete_records"
]
} batch_delete_records 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 multiple records at once (up to 10). 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 batch_delete_records: 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.
batch_delete_records 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 batch_delete_records 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 batch_delete_records. 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.
batch_delete_records 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.