Live fetch LinkedIn company. USE THIS WHEN: - Fetch live data from LinkedIn DO NOT USE FOR: - Batch operations (use search or batch APIs instead) EXAMPLE: Input: companyLiveEnrich_tool(apiKey="sk_live_...", type="example_string", value="example_string") INPUT SCHEMA: Required parameters: - ...
Handles credentials or secrets (apiKey)
Part of the Fiber MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents call companyLiveEnrich_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 companyLiveEnrich_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.
tools:
companyLiveEnrich_tool:
rules:
- action: allowSee the full Fiber policy for all 10 tools.
Agents calling read-class tools like companyLiveEnrich_tool have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.
Live fetch LinkedIn company. USE THIS WHEN: - Fetch live data from LinkedIn DO NOT USE FOR: - Batch operations (use search or batch APIs instead) EXAMPLE: Input: companyLiveEnrich_tool(apiKey="sk_live_...", type="example_string", value="example_string") INPUT SCHEMA: Required parameters: - apiKey (string): Your Fiber API key. Must start with 'sk_live_' or 'sk_test_'. Example: 'sk_live_dR6DxD3HT7oJqTEV' - type (string): - value (string): The company's LinkedIn slug (e.g., 'microsoft'), LinkedIn URL (e.g., 'https://www.linkedin.com/company/microsoft' or 'https://www.linkedin.com/company/1441'), LinkedIn organization ID (e.g., '1441' for Google), or Fiber company ID (e.g., 'comp_1441') Optional parameters: - getHistoricalHeadcount (boolean): If true, we will attempt to compute the company's historical employee count and recent growth trends. No extra cost, but may take longer. 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.
Add a rule in your Intercept YAML policy under the tools section for companyLiveEnrich_tool. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Fiber MCP server.
companyLiveEnrich_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 companyLiveEnrich_tool rule in your Intercept 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 Intercept policy for companyLiveEnrich_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.
companyLiveEnrich_tool is provided by the Fiber MCP server (fiberai/fiber-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept