AI agents use hunter_batch_task_create to create or update resources in Hunter — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Hunter environment.
The name indicates creating a new resource (a batch task) on the Hunter platform, which is a Write operation. Based on the server description context, this likely initiates a batch query or export task. Confidence is reduced because the description is empty, so exact behavior is inferred from name and sibling tools.
From the tool's definition Tool name 'hunter_batch_task_create' suggests creation of a batch task; server description mentions 'batch queries, and export tasks'
Attacks that exploit this kind of access
hunter_batch_task_create. It is categorised as a Write tool in the Hunter MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Hunter MCP server in PolicyLayer and add a rule for hunter_batch_task_create: 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_create 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 hunter_batch_task_create 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_create. 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_create 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →