This record as markdown: /tools/heznpc-airmcp/gws-people-search.md
What gws_people_search does on AirMCP
AI agents call gws_people_search 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 gws_people_search is rated Low
This tool retrieves contact information from Google's People/Contacts service. While it is a Read operation with no side effects, the severity is elevated to high because contact data is sensitive personal information (names, phone numbers, email addresses, relationship details).
From the tool's definition Tool name 'gws_people_search' and description 'Search contacts in Google People/Contacts' indicate querying contact data. The operation is read-only with no data modification, deletion, or execution of external actions.
Attacks that exploit this kind of access
The rule that runs gws_people_search 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 gws_people_search, this is the rule to start with:
gws_people_search 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 gws_people_search call is checked against it from then on.
Questions about gws_people_search
Search contacts in Google People/Contacts. 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 gws_people_search: 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.
gws_people_search 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 gws_people_search 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 gws_people_search. 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.
gws_people_search 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