Show index status: collections, document counts, and health information.
AI agents call status 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.
This tool queries and returns diagnostic/health information about the document explorer's internal state (collections, counts, health). It is a pure read operation with no capability to modify data, execute code, or trigger external actions. The information returned is metadata about the system itself, making it low severity in terms of misuse potential.
From the tool's definition Tool name 'status' and description 'Show index status: collections, document counts, and health information' indicate read-only retrieval of metadata about the document index. No side effects, modifications, or external operations.
Documented attack patterns abuse exactly the kind of access status 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 status:
{
"version": "1",
"default": "deny",
"tools": {
"status": {}
}
} status is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Show index status: collections, document counts, and health information. It is categorised as a Read tool in the MinerU Document Explorer MCP Server, which means it retrieves data without modifying state.
Register the MinerU Document Explorer MCP server in PolicyLayer and add a rule for status: 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.
status is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the status 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.
Set action: deny in the PolicyLayer policy for status. 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.
status 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.
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.