AI agents invoke process_document to trigger actions in MinerU MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
The tool name 'process_document' suggests it triggers document processing operations (execution of MinerU APIs, file manipulation), which falls under Execute. However, the description is empty, so the exact behavior is uncertain. Based on sibling tools (process_directory, process_document_lite, query_task_status) and server context, it likely submits or runs a document processing task — an external operation.
From the tool's definition Tool name 'process_document' on a server described as supporting document processing using MinerU APIs, with automatic splitting and merging of large files.
Documented attack patterns abuse exactly the kind of access process_document gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MinerU MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for process_document:
{
"version": "1",
"default": "deny",
"tools": {
"process_document": {
"limits": [
{
"counter": "process_document_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}process_document stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
process_document. It is categorised as a Execute tool in the MinerU MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the MinerU MCP Server MCP server in PolicyLayer and add a rule for process_document: 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 MCP Server. Nothing to install.
process_document is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the process_document 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 process_document. 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.
process_document is provided by the MinerU MCP Server MCP server (neosun100/mineru-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MinerU MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
6 MinerU MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.