Poll contact details fetching task. USE THIS WHEN: - Get email addresses from LinkedIn profiles DO NOT USE FOR: - Searching for people (use peopleSearch instead) - Company information (use companySearch or kitchenSinkCompany) EXAMPLE: Input: pollContactEnrichmentResult_tool(apiKey="sk_live_...", ...
Risk signalsHandles credentials or secrets (apiKey)
Part of the Fiber server.
Free to start. No card required.
AI agents call pollContactEnrichmentResult_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 pollContactEnrichmentResult_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": {
"pollContactEnrichmentResult_tool": {}
}
}See the full Fiber policy for all 10 tools.
These attack patterns abuse exactly the kind of access pollContactEnrichmentResult_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.
Poll contact details fetching task. USE THIS WHEN: - Get email addresses from LinkedIn profiles DO NOT USE FOR: - Searching for people (use peopleSearch instead) - Company information (use companySearch or kitchenSinkCompany) EXAMPLE: Input: pollContactEnrichmentResult_tool(apiKey="sk_live_...", taskId="example_string") INPUT SCHEMA: Required parameters: - apiKey (string): Your Fiber API key. Must start with 'sk_live_' or 'sk_test_'. Example: 'sk_live_dR6DxD3HT7oJqTEV' - taskId (string): Task ID from the "start fetching person's email & phone" endpoint Optional parameters: RETURNS: Response object with keys: output, chargeInfo, warnings 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 pollContactEnrichmentResult_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.
pollContactEnrichmentResult_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 pollContactEnrichmentResult_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 pollContactEnrichmentResult_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.
pollContactEnrichmentResult_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.