lei_hierarchy
Map a company's corporate family tree from the GLEIF relationship register (keyless, CC0 open data): given a company name or LEI, returns its direct parent, ultimate (top-of-tree) parent, and a list of its direct children/subsidiaries with the total subsidiary count. Answers 'who ultimately owns ...
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/lei-hierarchy.md
What lei_hierarchy does on Livedatalink
AI agents call lei_hierarchy 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 |
|---|---|---|---|
query | string | Yes | A company legal name (e.g. 'Apple Inc') or a 20-character LEI code. Names resolve to the top-ranked match. |
children_limit | number | — | Max direct children to list (default 15, max 50). The total count is always reported. |
Parameters from the server's own tool schema.
Why lei_hierarchy is rated Low
Even though lei_hierarchy only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs lei_hierarchy 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 lei_hierarchy, this is the rule to start with:
lei_hierarchy 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 lei_hierarchy call is checked against it from then on.
Questions about lei_hierarchy
Map a company's corporate family tree from the GLEIF relationship register (keyless, CC0 open data): given a company name or LEI, returns its direct parent, ultimate (top-of-tree) parent, and a list of its direct children/subsidiaries with the total subsidiary count. Answers 'who ultimately owns this company?' and 'what does this company own?' — core due-diligence and beneficial-ownership questions. Each node includes the LEI, legal name, and jurisdiction so you can drill further. Relationships GLEIF has no filing for are reported as 'none reported' (not an error). It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
lei_hierarchy accepts 2 parameters: query, children_limit. Required: query. 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 lei_hierarchy: 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.
lei_hierarchy 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 lei_hierarchy 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 lei_hierarchy. 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.
lei_hierarchy 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