Low Risk

doc_elements

Extract structured elements (tables, figures, equations) from a document. Requires cloud configuration for PDF. Docx/PPTX tables work locally.

How to control doc_elements ↓

AI agents call doc_elements 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 retrieves and parses structured data from documents (tables, figures, equations) without modifying, deleting, or executing anything. It is a read-only operation that queries document content. Severity is low because extraction of document metadata poses minimal risk; the worst outcome is information disclosure of content the agent already has access to.

From the tool's definition Tool description states 'Extract structured elements (tables, figures, equations) from a document' — extraction and retrieval without modification or deletion. The verb 'extract' and the focus on reading content align with the Read category.

Documented attack patterns abuse exactly the kind of access doc_elements 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 doc_elements:

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

doc_elements 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 doc_elements tool do? +

Extract structured elements (tables, figures, equations) from a document. Requires cloud configuration for PDF. Docx/PPTX tables work locally. 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 doc_elements? +

Register the MinerU Document Explorer MCP server in PolicyLayer and add a rule for doc_elements: 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 doc_elements? +

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

Can I rate-limit doc_elements? +

Yes. Add a rate_limit block to the doc_elements 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 doc_elements completely? +

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

doc_elements 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.