// SCAN REPORT

Luogu

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

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

Last updated: 29 Jun 2026

0 can modify or destroy data

11 read-only

11 tools total

Community server · catalogue entry verified 29/06/2026

How to control Luogu ↓

TOOL MAP

What Luogu exposes to your agents

Read (11) 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 Luogu

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

Cap read operations

{
  "luogu_fetch_problem": {
    "limits": [
      {
        "counter": "luogu_fetch_problem_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 Luogu — 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 LUOGU →

Instant setup, no code required.

FULL CATALOGUE

All 11 Luogu tools

READ 11 tools

Read luogu_fetch_problem Fetch a Luogu problem statement, formats, samples, tags, difficulty, and source URL by pid. Read luogu_fetch_problem_set Fetch a Luogu training/problem set and its problem summaries by id. Read luogu_find_related_problems Find related Luogu practice problems by mixing topic/pain-point recommendations with live keyword search. Read luogu_find_topic_problems Find Luogu practice problems for an algorithm topic using aliases, known Luogu tag ids, deduplication, and mat Read luogu_get_capabilities Report which LeetCode-style route capabilities are available, auth-required, or planned for Luogu. Read luogu_get_user_profile Fetch public Luogu user profile data by uid. Read luogu_list_algorithm_topics List canonical algorithm topics, aliases, and known Luogu tag ids used by the high-level topic search route. Read luogu_recommend_problems Recommend seed Luogu problems from a topic or student pain point, with search hints for further exploration. Read luogu_resolve_problem Resolve a Luogu problem from a URL, problem id, or title fragment, then fetch the problem details. Read luogu_search_problem_sets Search Luogu training/problem sets by keyword. By default, combines title-filtered official sets with selected Read luogu_search_problems Search Luogu problems by keyword. Use this before fetching a problem when you only know a topic or partial tit

FAQ

Questions about Luogu

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

The Luogu server is primarily read-only with 11 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 Luogu MCP server expose? +

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

How do I enforce a policy on Luogu? +

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

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

ENFORCE POLICY ON LUOGU →

Instant setup, no code required.

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