Look up or search the global LEI (Legal Entity Identifier) registry — the authoritative ISO 17442 directory of ~2.6M legal entities worldwide (GLEIF, CC0). Pass lei for an exact 20-character LEI, or query to search by legal/other name (ranked best-match). Filter name search by country (HQ ISO 2-l...
AI agents call business.lei to retrieve information from Mcp without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries publicly available legal entity identifier data from a read-only registry (GLEIF). It performs no modifications, deletions, or financial transactions. The use cases cited (canonicalize company names, resolve counterparties, enrich vendor data) are all informational lookups.
From the tool's definition Tool performs lookups and searches on the LEI registry: 'Look up or search the global LEI registry', 'Pass lei for an exact 20-character LEI, or query to search by legal/other name'.
Attacks that exploit this kind of access
Look up or search the global LEI (Legal Entity Identifier) registry — the authoritative ISO 17442 directory of ~2.6M legal entities worldwide (GLEIF, CC0). Pass lei for an exact 20-character LEI, or query to search by legal/other name (ranked best-match). Filter name search by country (HQ ISO 2-letter) and status (active|all). Returns LEI, legal name, jurisdiction, entity category, legal-form code, entity + registration status, HQ address, registration/renewal dates, and managing LOU. Canonicalize a company name to its LEI, resolve a counterparty, or enrich a vendor master. It is categorised as a Read tool in the Mcp MCP Server, which means it retrieves data without modifying state.
Register the MCP server in PolicyLayer and add a rule for business.lei: 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 Mcp. Nothing to install.
business.lei 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 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. 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 is provided by the MCP server (@2sio/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →