People search. USE THIS WHEN: - Search for people/profiles DO NOT USE FOR: - Getting email/phone directly (use syncContactEnrichment after finding profile) - Company searches (use companySearch) EXAMPLE: Input: peopleSearch_tool(apiKey="sk_live_...", searchParams={}, pageSize=123) INPUT SCHEMA: R...
Risk signalsHandles credentials or secrets (apiKey)
Part of the Fiber server.
Free to start. No card required.
AI agents call peopleSearch_tool to retrieve information from Fiber without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though peopleSearch_tool only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"peopleSearch_tool": {}
}
}See the full Fiber policy for all 10 tools.
These attack patterns abuse exactly the kind of access peopleSearch_tool gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
People search. USE THIS WHEN: - Search for people/profiles DO NOT USE FOR: - Getting email/phone directly (use syncContactEnrichment after finding profile) - Company searches (use companySearch) EXAMPLE: Input: peopleSearch_tool(apiKey="sk_live_...", searchParams={}, pageSize=123) INPUT SCHEMA: Required parameters: - apiKey (string): Your Fiber API key. Must start with 'sk_live_' or 'sk_test_'. Example: 'sk_live_dR6DxD3HT7oJqTEV' Optional parameters: - searchParams (object): Search parameters for people search. - country3LetterCode (['object', 'null']) - numConnections (['object', 'null']) - numFollowers (['object', 'null']) - approxAge (['object', 'null']) - keywords (['object', 'null']) - keywordSearchOptions (['object', 'null']) - jobTitleV2 (['object', 'null']) - exactProfile (['object', 'null']) - startedInRole (any) - startedAtCompany (any) - location (['object', 'null']) - pastJobs (['object', 'null']) - languages (['object', 'null']) - leftStealthAt (any) - isInStealth (['boolean', 'null']) - stealthV2 (any) - jobStatus (any) - timeZone (['object', 'null']) - pastJobText (['object', 'null']) - fuzzyName (['object', 'null']) - companyMatchMode (any) - yearsOfExperience (['object', 'null']) - jobTitleV3 (['object', 'null']) - hasProfilePicture (['boolean', 'null']) - state (['object', 'null']) - getDetailedEducation (['boolean', 'null']) - getDetailedWorkExperience (['boolean', 'null']) - tags (['object', 'null']) - education (['object', 'null']) - pageSize (integer): The number of profiles to return, if you need to get more results, you can paginate. - cursor (['string', 'null']): A pagination cursor returned from a previous search response. Use this to fetch the next page of results. - currentCompanies (['array', 'null']): Filter people by the companies they are currently working for. If you want to search over many companies, we suggest using the Combined Search API, which is optimized for this use case. - prospectExclusionListIDs (['array', 'null']): Filter out people which belong to the given prospect exclusion lists - companyExclusionListIDs (['array', 'null']): Filter out people who work at companies which belong to the given company exclusion lists RETURNS: Response object with keys: output, chargeInfo, warnings PERFORMANCE HINT: - Set pageSize=1 to avoid overwhelming the LLM with too much data. - Only request more if specifically asked by the user. COMMON MISTAKES: - Missing apiKey in function call (apiKey is required) - Invalid API key format (must be 18-50 characters) - API key not in request body (always pass as parameter). It is categorised as a Read tool in the Fiber MCP Server, which means it retrieves data without modifying state.
Register the Fiber MCP server in PolicyLayer and add a rule for peopleSearch_tool: 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 Fiber. Nothing to install.
peopleSearch_tool 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 peopleSearch_tool 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 peopleSearch_tool. 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.
peopleSearch_tool is provided by the Fiber MCP server (fiberai/fiber-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 10 Fiber tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.