Get full details of a single e-RUP entity.
AI agents call get_entity to retrieve information from e-RUP KNF MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool simply fetches and returns information about a registered payment institution entity. It has no side effects, does not modify data, execute code, or trigger external actions. The worst-case misuse scenario is unauthorized information disclosure of public registry data, which is a low-severity risk since the e-RUP is a public registry maintained by the Polish financial regulator (KNF).
From the tool's definition The tool 'get_entity' retrieves 'full details of a single e-RUP entity' from the Polish KNF payment institution registry. This is a query/retrieval operation with no modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
Get full details of a single e-RUP entity. It is categorised as a Read tool in the e-RUP KNF MCP Server MCP Server, which means it retrieves data without modifying state.
Register the e-RUP KNF MCP Server MCP server in PolicyLayer and add a rule for get_entity: 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 e-RUP KNF MCP Server. Nothing to install.
get_entity 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_entity 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_entity. 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_entity is provided by the e-RUP KNF MCP Server MCP server (kymylyy/erup2.0-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 →