Write a markdown document to a QMD collection. Creates or overwrites the file on disk, then immediately re-indexes it (FTS + links). Does NOT generate embeddings — run
AI agents use doc_write to create or update resources in MinerU Document Explorer — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MinerU Document Explorer environment.
This tool creates or modifies files on disk and triggers re-indexing. While not destructive (the original can be recovered), it is clearly a Write operation because it persistently alters data in a collection. The high severity reflects that an AI agent could overwrite important documents, corrupt knowledge bases, or inject malicious content into indexed collections.
From the tool's definition Tool name 'doc_write' and description explicitly states it 'Write[s] a markdown document' and 'Creates or overwrites the file on disk'.
Documented attack patterns abuse exactly the kind of access doc_write 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_write:
{
"version": "1",
"default": "deny",
"tools": {
"doc_write": {
"limits": [
{
"counter": "doc_write_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}doc_write stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Write a markdown document to a QMD collection. Creates or overwrites the file on disk, then immediately re-indexes it (FTS + links). Does NOT generate embeddings — run. It is categorised as a Write tool in the MinerU Document Explorer MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MinerU Document Explorer MCP server in PolicyLayer and add a rule for doc_write: 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.
doc_write is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the doc_write 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 doc_write. 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.
doc_write 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.