// SCAN REPORT

UluVoiMCP

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

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

Last updated: 3 Jul 2026

0 can modify or destroy data

10 read-only

10 tools total

Community server · catalogue entry verified 03/07/2026

How to control UluVoiMCP ↓

TOOL MAP

What UluVoiMCP exposes to your agents

Read (10) 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 UluVoiMCP

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

Cap read operations

{
  "get_contract_role": {
    "limits": [
      {
        "counter": "get_contract_role_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 UluVoiMCP — 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 ULUVOIMCP →

Instant setup, no code required.

FULL CATALOGUE

All 10 UluVoiMCP tools

READ 10 tools

Read get_contract_role Get the role and purpose of a specific contract on Voi (e.g. liquidity-pool, bridge, registry) Read get_protocol Get detailed information about a specific Voi ecosystem protocol by ID Read get_protocol_contracts List all known application contracts for a Voi protocol Read get_protocol_summary Get a human-readable summary of a Voi protocol including its purpose, contracts, and assets Read get_protocols List all known Voi ecosystem protocols with type and description Read identify_application Identify a Voi application by ID — returns protocol, role, type, and description if known Read identify_asset Identify a Voi asset by ID — returns name, symbol, type, protocol, and category if known Read resolve_name Resolve an enVoi name (e.g. Read reverse_resolve_address Look up well-known enVoi names associated with a Voi address from the static registry. For live resolution, us Read search_names Search the static enVoi name registry by pattern. For live search, use UluCoreMCP

FAQ

Questions about UluVoiMCP

Is the UluVoi MCP server safe to use without restrictions? +

The UluVoiMCP server is primarily read-only with 10 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 UluVoi MCP server expose? +

10 tools across 2 categories: Read, Write. 10 are read-only. 0 can modify, create, or delete data.

How do I enforce a policy on UluVoiMCP? +

Register the UluVoi 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 UluVoiMCP tool call.

Deterministic rules across all 10 UluVoiMCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON ULUVOIMCP →

Instant setup, no code required.

10 UluVoiMCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.