business.lei.relationships
Find the direct parent company of a legal entity by LEI code — returns parent LEI, relationship type, and status. Useful for corporate ownership chain analysis (GLEIF)
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/business.lei.relationships.md
What business.lei.relationships does on Apibase
AI agents call business.lei.relationships to retrieve information from Apibase 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 |
|---|---|---|---|
lei | string | Yes | LEI code to find parent company relationship for |
Parameters from the server's own tool schema.
Why business.lei.relationships is rated Low
Queries corporate relationship data without modification, deletion, or financial transactions.
From the tool's definition Find the direct parent company by LEI code — returns parent LEI, relationship type, and status.
Attacks that exploit this kind of access
The rule that runs business.lei.relationships safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For business.lei.relationships, this is the rule to start with:
business.lei.relationships 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 Apibase, apply this rule, and every business.lei.relationships call is checked against it from then on.
Questions about business.lei.relationships
Find the direct parent company of a legal entity by LEI code — returns parent LEI, relationship type, and status. Useful for corporate ownership chain analysis (GLEIF). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
business.lei.relationships accepts 1 parameter: lei. Required: lei. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for business.lei.relationships: 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 Apibase. Nothing to install.
business.lei.relationships 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 business.lei.relationships 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 business.lei.relationships. 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.
business.lei.relationships is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue