person.cross-registry
Sweep a person name across five US public registries in one call: FINRA brokers, federal-court attorneys, federal inmates (BOP), Texas trade licenses, Texas real-estate licenses. Per-registry found/error blocks with matching records — name-matched CANDIDATES, not identity-resolved (verify with ea...
This record as markdown: /tools/io-github-2s-io-mcp/person.cross-registry.md
What person.cross-registry does on Mcp
AI agents call person.cross-registry 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.
Why person.cross-registry is rated Low
This is fundamentally a Read operation: it queries multiple public data sources and returns matching records without modifying, creating, deleting, or executing anything.
From the tool's definition Tool 'person.cross-registry' retrieves and queries data across five US public registries (FINRA brokers, federal-court attorneys, federal inmates, Texas trade licenses, Texas real-estate licenses).
Attacks that exploit this kind of access
The rule that runs person.cross-registry 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 person.cross-registry, this is the rule to start with:
person.cross-registry 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 Mcp, apply this rule, and every person.cross-registry call is checked against it from then on.
Questions about person.cross-registry
Sweep a person name across five US public registries in one call: FINRA brokers, federal-court attorneys, federal inmates (BOP), Texas trade licenses, Texas real-estate licenses. Per-registry found/error blocks with matching records — name-matched CANDIDATES, not identity-resolved (verify with each registry\. 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 person.cross-registry: 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.
person.cross-registry 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 person.cross-registry 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 person.cross-registry. 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.
person.cross-registry 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.
More on , and thousands of servers like it.
This server
Across the catalogue