Fuzzy entity resolution: resolve a messy, free-text company name to its canonical GLEIF Legal Entity Identifier (LEI) with a 0-1 similarity score and high/medium/low confidence. Tolerant of legal-suffix noise (Inc/Ltd/GmbH/S.A.), word order, ampersands, punctuation, and former/alternate names (e.g.
AI agents call business.entity-match 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 queries and retrieves canonical company identifiers (LEI codes) based on fuzzy matching of company names against a reference database. It is purely informational—it searches, matches, and returns data with no side effects, no state changes, and no irreversible actions. This is a classic Read operation: a lookup/resolution service with output-only impact.
From the tool's definition Fuzzy entity resolution: resolve a messy, free-text company name to its canonical GLEIF Legal Entity Identifier (LEI) with a 0-1 similarity score and high/medium/low confidence.
Attacks that exploit this kind of access
Fuzzy entity resolution: resolve a messy, free-text company name to its canonical GLEIF Legal Entity Identifier (LEI) with a 0-1 similarity score and high/medium/low confidence. Tolerant of legal-suffix noise (Inc/Ltd/GmbH/S.A.), word order, ampersands, punctuation, and former/alternate names (e.g. 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.entity-match: 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.entity-match 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.entity-match 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.entity-match. 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.entity-match 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 →