// SCAN REPORT

e-RUP KNF MCP Server

8 tools. 0 can modify or destroy data without limits.

Read-only server. Low risk, but rate limits prevent runaway API costs.

Last updated: 2 Jul 2026

0 can modify or destroy data

8 read-only

8 tools total

Community server · catalogue entry verified 02/07/2026

How to control e-RUP KNF MCP Server ↓

TOOL MAP

What e-RUP KNF MCP Server exposes to your agents

Read (8) Write / Execute (0) Destructive / Financial (0)

Running more than one server? Check your whole stack →

THE RISK

What can go wrong

Even read-only tools carry cost. An agent in a retry loop can make thousands of API calls per minute, exhausting rate limits and running up bills.

POLICY

How to control e-RUP KNF MCP Server

PolicyLayer is an MCP gateway — it sits between your AI agents and e-RUP KNF MCP Server, and nothing reaches the server without passing your rules. These are the rules we recommend:

Cap read operations

{
  "get_entity": {
    "limits": [
      {
        "counter": "get_entity_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register e-RUP KNF MCP Server — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON E-RUP KNF →

Instant setup, no code required.

FULL CATALOGUE

All 8 e-RUP KNF MCP Server tools

READ 8 tools

Read get_entity Get full details of a single e-RUP entity. Read get_entity_agents Get agents associated with an entity. Read get_entity_branches Get branches associated with an entity. Read get_entity_history Get status history for an e-RUP entity. Read get_entity_services Get payment service authorizations for an entity. Read get_registry_stats Return only the count of entities matching optional filters. Read list_entity_types List all entity type codes and descriptions from KNF taxonomy. Read search_entities Search and filter entities in the KNF e-RUP registry.

FAQ

Questions about e-RUP KNF MCP Server

Is the e-RUP KNF MCP Server MCP server safe to use without restrictions? +

The e-RUP KNF MCP Server server is primarily read-only with 8 read tools. While it cannot modify data, an agent in a retry loop can make thousands of API calls per minute, exhausting rate limits and running up costs. Rate limiting is still recommended.

How many tools does the e-RUP KNF MCP Server MCP server expose? +

8 tools across 1 categories: Read. 8 are read-only. 0 can modify, create, or delete data.

How do I enforce a policy on e-RUP KNF MCP Server? +

Register the e-RUP KNF MCP Server MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every e-RUP KNF MCP Server tool call.

Deterministic rules across all 8 e-RUP KNF MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON E-RUP KNF →

Instant setup, no code required.

8 e-RUP KNF MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.