entity_dossier
Build a consolidated cross-source dossier for a company in one call: SEC registration and identifiers (EDGAR), environmental footprint and regulated facilities (EPA ECHO), and sanctions/denied-party screening (OFAC/UN/EU/BIS) with a confidence score. Returns a per-source summary plus top records....
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/entity-dossier.md
What entity_dossier does on Livedatalink
AI agents call entity_dossier to retrieve information from Livedatalink without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | Yes | Company / organization name, e.g. 'Chevron Corporation', 'Acme Trucking LLC'. |
limit | number | — | Max records to surface per source (default 5, max 15). |
state | string | — | Optional 2-letter US state to disambiguate location-based sources (e.g. 'TX'). |
Parameters from the server's own tool schema.
Why entity_dossier is rated Low
This tool retrieves and aggregates publicly available regulatory data (SEC/EDGAR, EPA ECHO, OFAC/UN/EU/BIS sanctions) about a company. It performs no writes, executions, or financial transactions.
From the tool's definition Build a consolidated cross-source dossier... Returns a per-source summary plus top records... single AI-native lookup across data
Attacks that exploit this kind of access
The rule that runs entity_dossier safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Livedatalink, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For entity_dossier, this is the rule to start with:
entity_dossier is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Livedatalink, apply this rule, and every entity_dossier call is checked against it from then on.
Questions about entity_dossier
Build a consolidated cross-source dossier for a company in one call: SEC registration and identifiers (EDGAR), environmental footprint and regulated facilities (EPA ECHO), and sanctions/denied-party screening (OFAC/UN/EU/BIS) with a confidence score. Returns a per-source summary plus top records. This is a single AI-native lookup across data that otherwise lives in separate silos. Matches are name-based; verify identity before relying on any link. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
entity_dossier accepts 3 parameters: name, limit, state. Required: name. The full parameter table on this page comes from the server's own tool schema.
Register the Livedatalink MCP server in PolicyLayer and add a rule for entity_dossier: 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 Livedatalink. Nothing to install.
entity_dossier 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 entity_dossier 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 entity_dossier. 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.
entity_dossier is provided by the Livedatalink MCP server (https://livedatalink.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Livedatalink, and thousands of servers like it.
This server
Across the catalogue