Low Risk

query_task_status

query_task_status

How to control query_task_status ↓

What query_task_status does on MinerU MCP Server

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

Low Risk

Why query_task_status needs a policy

A task status query is fundamentally a read operation that retrieves information about previously initiated processing tasks. Even with an empty description, the semantic meaning of 'query_task_status' aligns with Read operations (retrieve, query). No side effects are implied.

From the tool's definition Tool name 'query_task_status' indicates a status query operation; description is empty but the name and sibling tool names (process_document, process_directory, get_token_status) suggest this retrieves task state without modification.

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

How to control query_task_status

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 query_task_status:

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

query_task_status 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 MCP Server — 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.

Related tools and policies

Go deeper

Questions about query_task_status

What does the query_task_status tool do? +

query_task_status. It is categorised as a Read tool in the MinerU MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on query_task_status? +

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

What risk level is query_task_status? +

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

Can I rate-limit query_task_status? +

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

How do I block query_task_status completely? +

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

What MCP server provides query_task_status? +

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

Enforce policy on every MinerU MCP Server tool call.

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.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.