Low Risk

wiki_lint

Health-check the wiki. Analyzes the link graph to find: - Orphan pages (no inbound links) - Broken links (targets that don

How to control wiki_lint ↓

AI agents call wiki_lint to retrieve information from MinerU Document Explorer without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

This tool only reads and analyzes existing wiki structure without creating, modifying, or deleting content. It has no side effects beyond retrieving information to report. The description cuts off but indicates detection of issues rather than remediation. This is purely informational analysis, fitting the Read category with low severity since the blast radius of misuse is limited to accessing diagnostic metadata.

From the tool's definition wiki_lint performs analysis and health-checking of link graphs to find orphan pages and broken links. The tool 'Analyzes' and 'find[s]' issues without modifying, deleting, or executing code.

Documented attack patterns abuse exactly the kind of access wiki_lint gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and MinerU Document Explorer, and nothing reaches the server without passing your rules. This is the rule we recommend for wiki_lint:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "wiki_lint": {}
  }
}

wiki_lint is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register MinerU Document Explorer — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the wiki_lint tool do? +

Health-check the wiki. Analyzes the link graph to find: - Orphan pages (no inbound links) - Broken links (targets that don. It is categorised as a Read tool in the MinerU Document Explorer MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on wiki_lint? +

Register the MinerU Document Explorer MCP server in PolicyLayer and add a rule for wiki_lint: 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 MinerU Document Explorer. Nothing to install.

What risk level is wiki_lint? +

wiki_lint is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit wiki_lint? +

Yes. Add a rate_limit block to the wiki_lint 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.

How do I block wiki_lint completely? +

Set action: deny in the PolicyLayer policy for wiki_lint. 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.

What MCP server provides wiki_lint? +

wiki_lint is provided by the MinerU Document Explorer MCP server (opendatalab/mineru-document-explorer). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every MinerU Document Explorer tool call.

Deterministic rules across all 15 MinerU Document Explorer tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

15 MinerU Document Explorer tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.