get_beneficiary
AI agents call get_beneficiary 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.
The tool retrieves beneficiary data from a public business registry without modifying, deleting, or executing operations. It is a Read operation. Severity is medium because beneficiary information (beneficial ownership data) is sensitive PII that could enable identity theft, targeted fraud, or competitive intelligence if exposed to unauthorized agents, though it is sourced from a public registry.
From the tool's definition Tool name 'get_beneficiary' indicates retrieval of beneficiary information; server description states it enables 'beneficiary checks' and 'company search' via natural language queries; tool description is empty but sibling tools (get_company_info_*,…
Attacks that exploit this kind of access
get_beneficiary. It is categorised as a Read tool in the Rejestr Io MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Rejestr Io MCP Server MCP server in PolicyLayer and add a rule for get_beneficiary: 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.
get_beneficiary 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 get_beneficiary 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 get_beneficiary. 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.
get_beneficiary 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.
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 →