Get payment service authorizations for an entity.
AI agents call get_entity_services 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 retrieves information about payment service authorizations for a specific entity from the Polish KNF e-RUP registry. It performs a lookup query with no capability to create, modify, delete, or execute operations. The data returned is static registry information. The blast radius of misuse is minimal—an agent could only access existing public regulatory information about payment institutions.
From the tool's definition Tool name 'get_entity_services' and description 'Get payment service authorizations for an entity' indicate a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
Get payment service authorizations for an 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_services: 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_services 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_services 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_services. 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_services 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 →