This record as markdown: /tools/heznpc-airmcp/search-contacts.md
What search_contacts does on AirMCP
AI agents call search_contacts 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_contacts is rated Low
This tool retrieves contact data based on search criteria without creating, modifying, or deleting any information. It is a straightforward read-only operation with no side effects beyond returning matching contact records. The severity is low because contact search data is typically low-sensitivity metadata, though exposure could reveal organizational structure or personal relationships if misused at scale.
From the tool's definition Tool name is 'search_contacts' and description states it 'Search contacts by name, email, phone, or organization' — a pure query operation with no modification, deletion, or execution of code.
Attacks that exploit this kind of access
The rule that runs search_contacts 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_contacts, this is the rule to start with:
search_contacts 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_contacts call is checked against it from then on.
Questions about search_contacts
Search contacts by name, email, phone, or organization. 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_contacts: 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_contacts 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_contacts 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_contacts. 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_contacts 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