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...
Risk signalsHandles credentials or secrets (apiKey)
Part of the Fiber server.
Free to start. No card required.
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.
{
"version": "1",
"default": "deny",
"tools": {
"companyLiveEnrich_tool": {}
}
}See the full Fiber policy for all 10 tools.
These attack patterns abuse exactly the kind of access companyLiveEnrich_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.
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.
Register the Fiber MCP server in PolicyLayer and add a rule for companyLiveEnrich_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.
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 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 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). 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.