business.entity-screen

KYC in one call: look up a business in a US state registry (NY/CO/CT) AND screen it + its registered agent against OFAC sanctions. Returns matched entities each with a sanctions screen (confidence + flagged). Counterparty due-diligence, AML. Probabilistic name match.

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-screen.md

WHAT IT DOES

What business.entity-screen does on Mcp

AI agents call business.entity-screen 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-screen is rated Low

This is a KYC/AML lookup and screening tool that retrieves and cross-references data from public registries and OFAC sanctions lists. While the information it returns informs compliance decisions, the tool itself performs read-only queries without side effects. There is no creation, modification, deletion of records, code execution, or financial transaction.

From the tool's definition 'look up a business in a US state registry' and 'screen it...against OFAC sanctions' — both retrieval and screening operations with no data modification.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs business.entity-screen 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-screen, this is the rule to start with:

business.entity-screen Allowed

business.entity-screen 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-screen": {}
  }
}

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-screen call is checked against it from then on.

FAQ

Questions about business.entity-screen

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

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

Register the MCP server in PolicyLayer and add a rule for business.entity-screen: 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-screen? +

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

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

Yes. Add a rate_limit block to the business.entity-screen 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-screen completely? +

Set action: deny in the PolicyLayer policy for business.entity-screen. 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-screen? +

business.entity-screen 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

The MCP Attack Database →

Guides

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