AI agents call search_records to retrieve information from Airtable MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries data from Airtable with no side effects. It does not create, modify, delete, or execute code. Despite the server supporting destructive operations (batch_delete_records, create_base, etc.), this specific tool is limited to searching and returning results, making it a Read category risk.
From the tool's definition Tool name 'search_records' and description 'Search records with filtering and sorting' indicate data retrieval without modification. The verb 'search' combined with 'filtering and sorting' are classic read-only operations.
Documented attack patterns abuse exactly the kind of access search_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 search_records:
{
"version": "1",
"default": "deny",
"tools": {
"search_records": {}
}
}search_records is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Search records with filtering and sorting. It is categorised as a Read tool in the Airtable MCP MCP Server, which means it retrieves data without modifying state.
Register the Airtable MCP server in PolicyLayer and add a rule for search_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.
search_records is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the search_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 search_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.
search_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.