AI agents call people_search to retrieve information from Apollo Io MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool searches for and retrieves people data from Apollo.io. It performs a read-only query operation with no side effects, data modification, or irreversible actions. The low severity reflects minimal risk even if misused by an AI agent, as it only returns existing information without creating, modifying, or deleting records.
From the tool's definition Tool name 'people_search' and description 'Use the People Search endpoint to find people' indicate a query/retrieval operation with no modification of data.
Documented attack patterns abuse exactly the kind of access people_search gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Apollo Io MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for people_search:
{
"version": "1",
"default": "deny",
"tools": {
"people_search": {}
}
} people_search 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.
Use the People Search endpoint to find people. It is categorised as a Read tool in the Apollo Io MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Apollo Io MCP Server MCP server in PolicyLayer and add a rule for 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 Apollo Io MCP Server. Nothing to install.
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 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 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.
people_search is provided by the Apollo Io MCP Server MCP server (lkm1developer/apollo-io-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Apollo Io MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
7 Apollo Io MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.