AI agents call hunter_batch_task_progress to retrieve information from Hunter without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves the progress status of an existing batch task. It performs a read-only operation to fetch information about task execution state. There is no data creation, modification, deletion, code execution, or financial transaction involved. The tool merely returns progress information, making it a straightforward Read category classification.
From the tool's definition Tool name 'hunter_batch_task_progress' and description '查看 Qianxin Hunter 批量查询任务的执行进度' (View the execution progress of Qianxin Hunter batch query tasks) indicates retrieval of task status information without modification or side effects.
Attacks that exploit this kind of access
查看 Qianxin Hunter 批量查询任务的执行进度。. It is categorised as a Read tool in the Hunter MCP Server, which means it retrieves data without modifying state.
Register the Hunter MCP server in PolicyLayer and add a rule for hunter_batch_task_progress: 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 Hunter. Nothing to install.
hunter_batch_task_progress 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 hunter_batch_task_progress 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 hunter_batch_task_progress. 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.
hunter_batch_task_progress is provided by the Hunter MCP server (piggyhurry/hunter-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
hunter_batch_task_progress is one line of Hunter's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →