Search and filter entities in the KNF e-RUP registry.
AI agents call search_entities 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 and filters data from a registry with no capability to modify, delete, or execute operations. It is a straightforward read operation that produces no side effects. The low severity reflects that misuse would only result in information disclosure from a payment institution registry, not unauthorized modifications or financial impact.
From the tool's definition Tool description states 'Search and filter entities in the KNF e-RUP registry' with no mention of modification, deletion, or execution capabilities. All sibling tools are also read-only queries (get_*, list_*).
Attacks that exploit this kind of access
Search and filter entities in the KNF e-RUP registry. 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 search_entities: 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.
search_entities 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 search_entities 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 search_entities. 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.
search_entities 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 →