get_connections_by_person

get_connections_by_person

Server Rejestr Io MCP Server kolegaliterat/rejestr-io-mcp
Category Read
Risk class Low
Parameters 00 required

What get_connections_by_person does on Rejestr Io MCP Server

AI agents call get_connections_by_person to retrieve information from Rejestr Io MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why get_connections_by_person needs a policy

The tool follows the pattern of sibling tools (get_beneficiary, get_company_info_*) which are all read operations querying the registry database. The name suggests it retrieves existing connection data without modification. However, confidence is moderate (0.75) rather than high because the description is empty, leaving some ambiguity about exact scope and whether it might expose sensitive personal network data.

From the tool's definition Tool name 'get_connections_by_person' indicates data retrieval. The server provides 'access to Poland's largest business registry database, enabling company search, beneficiary checks, and financial document retrieval.' This tool appears to retrieve…

Questions about get_connections_by_person

What does the get_connections_by_person tool do? +

get_connections_by_person. It is categorised as a Read tool in the Rejestr Io MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_connections_by_person? +

Register the Rejestr Io MCP Server MCP server in PolicyLayer and add a rule for get_connections_by_person: 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 Rejestr Io MCP Server. Nothing to install.

What risk level is get_connections_by_person? +

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

Can I rate-limit get_connections_by_person? +

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

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

get_connections_by_person is provided by the Rejestr Io MCP Server MCP server (kolegaliterat/rejestr-io-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.