Search for sales prospects by role, industry, company size, and location. Returns matching contacts with names, titles, companies, and LinkedIn URLs. e.g., role=CTO, industry=SaaS, company_size=50-200 returns 10 CTOs at mid-size SaaS companies. Use this to build a prospect list from scratch; use ...
AI agents call search_prospects to retrieve information from Sales Prospector without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries a database to retrieve prospect information based on filter criteria (role, industry, company size, location). It has no capability to modify data, execute operations, delete records, or move money. The results are read-only contact records. While the tool supports sales prospecting workflows, its core function is passive data retrieval.
From the tool's definition Tool description states it 'Search[es] for sales prospects' and 'Returns matching contacts with names, titles, companies, and LinkedIn URLs.' The verb 'search' and 'returns' indicate data retrieval with no modification or side effects.
Attacks that exploit this kind of access
Search for sales prospects by role, industry, company size, and location. Returns matching contacts with names, titles, companies, and LinkedIn URLs. e.g., role=CTO, industry=SaaS, company_size=50-200 returns 10 CTOs at mid-size SaaS companies. Use this to build a prospect list from scratch; use find_company_contacts when you already know the target company. It is categorised as a Read tool in the Sales Prospector MCP Server, which means it retrieves data without modifying state.
Register the Sales Prospector MCP server in PolicyLayer and add a rule for search_prospects: 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 Sales Prospector. Nothing to install.
search_prospects 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_prospects 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_prospects. 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_prospects is provided by the Sales Prospector MCP server (josephtandle/apollo-mcp-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →