This record as markdown: /tools/heznpc-airmcp/search-chats.md
What search_chats does on AirMCP
AI agents call search_chats to retrieve information from AirMCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why search_chats is rated Low
This tool retrieves or queries chat data based on search criteria without creating, modifying, deleting, or executing any operations. It is a straightforward information retrieval function with minimal blast radius if misused—an AI agent could discover chats but cannot alter or delete them.
From the tool's definition The tool description explicitly states it 'Search[es] chats' by various attributes (participant name, handle, or chat name), indicating a read-only query operation with no data modification or destructive capability.
Attacks that exploit this kind of access
The rule that runs search_chats safely
PolicyLayer is an MCP gateway: it sits between your AI agents and AirMCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For search_chats, this is the rule to start with:
search_chats is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect AirMCP, apply this rule, and every search_chats call is checked against it from then on.
Questions about search_chats
Search chats by participant name, handle, or chat name. It is categorised as a Read tool in the AirMCP MCP Server, which means it retrieves data without modifying state.
Register the Air MCP server in PolicyLayer and add a rule for search_chats: 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 AirMCP. Nothing to install.
search_chats 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_chats 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_chats. 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_chats is provided by the Air MCP server (airmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Air, and thousands of servers like it.
This server
Across the catalogue