Get branches associated with an entity.
AI agents call get_entity_branches 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 branch information linked to a payment institution entity from the Polish KNF registry. It has no side effects—it queries and returns existing data without creating, modifying, deleting, or executing any operations. The context (e-RUP registry of payment institutions) reinforces that this is a public registry lookup with no destructive or financial impact.
From the tool's definition Tool name 'get_entity_branches' and description 'Get branches associated with an entity' indicate a retrieval operation. The verb 'Get' and the action of fetching associated data without modification confirm this is a read-only query.
Attacks that exploit this kind of access
Get branches associated with 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_branches: 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_branches 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_branches 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_branches. 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_branches 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 →