business.entity-match

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.

SERVERMcp SOURCE@2sio/mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-2s-io-mcp/business.entity-match.md

WHAT IT DOES

What business.entity-match does on Mcp

AI agents call business.entity-match to retrieve information from Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why business.entity-match is rated Low

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

RECOMMENDED RULE

The rule that runs business.entity-match safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For business.entity-match, this is the rule to start with:

business.entity-match Allowed

business.entity-match is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "business.entity-match": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Mcp, apply this rule, and every business.entity-match call is checked against it from then on.

FAQ

Questions about business.entity-match

What does the business.entity-match tool do? +

How do I enforce a policy on business.entity-match? +

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.

What risk level is business.entity-match? +

business.entity-match is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit business.entity-match? +

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.

How do I block business.entity-match completely? +

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.

What MCP server provides business.entity-match? +

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.

KEEP EXPLORING

More on , and thousands of servers like it.

This server

All 572 tools →

Across the catalogue

match_agent on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →