// SCAN REPORT

LI FI

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

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

Last updated:

0 can modify or destroy data
25 read-only
25 tools total

LI FI is read-only, but an agent in a loop can still exhaust your rate limits and budget. PolicyLayer caps every call before it runs. Live in minutes.

SECURE LI FI →

Free to start. No card required.

TOOL MAP

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

CONTEXT-WINDOW COST

5,115 tokens of tool definitions, loaded on every request
2.6% of a 200k context window
756 heaviest tool: get-quote

Full per-tool breakdown → Model it in the token calculator →

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.

RECOMMENDED RULES

Cap read operations
{
  "get-allowance": {
    "limits": [
      {
        "counter": "get-allowance_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

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

Get this policy live on your own LI FI server in minutes. Tune the limits to your setup; PolicyLayer enforces it on every call.

ENFORCE ON MY LI FI →

ALL 25 LI FI TOOLS

READ 25 tools
Read get-allowance Read get-chain-by-id Read get-chain-by-name Read get-chains Read get-connections Read get-earn-chains Read get-earn-portfolio Read get-earn-protocols Read get-earn-vault Read get-earn-vaults Read get-gas-prices Read get-gas-suggestion Read get-native-token-balance Read get-quote Read get-quote-with-calls Read get-routes Read get-status Read get-step-transaction Read get-token Read get-token-balance Read get-token-balances Read get-tokens Read get-tools Read health-check Read test-api-key

FAQ

Is the LI FI MCP server safe to use without restrictions? +

The LI FI server is primarily read-only with 25 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 LI FI MCP server expose? +

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

How do I enforce a policy on LI FI? +

Register the LI FI 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 LI FI tool call.

Deterministic rules across all 25 LI FI tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

SECURE LI FI →

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.