Create multiple candidates in a single operation
AI agents use bulk_create_candidates to create or update resources in MCP Ashby Connector — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Ashby Connector environment.
This tool creates new candidate records in Ashby's ATS, which is a write operation that modifies data reversibly. While bulk operations affect multiple records, candidate creation can be undone through deletion. Severity is medium because creating invalid or spam candidates could pollute the recruiting database and cause operational friction, but does not result in irreversible loss or financial impact per se.
From the tool's definition Tool name contains 'create' and description states 'Create multiple candidates in a single operation', indicating it creates/adds new records in bulk to the ATS system.
Documented attack patterns abuse exactly the kind of access bulk_create_candidates gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Ashby Connector, and nothing reaches the server without passing your rules. This is the rule we recommend for bulk_create_candidates:
{
"version": "1",
"default": "deny",
"tools": {
"bulk_create_candidates": {
"limits": [
{
"counter": "bulk_create_candidates_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} bulk_create_candidates 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.
Create multiple candidates in a single operation. It is categorised as a Write tool in the MCP Ashby Connector MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Ashby Connector MCP server in PolicyLayer and add a rule for bulk_create_candidates: 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 MCP Ashby Connector. Nothing to install.
bulk_create_candidates 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 bulk_create_candidates 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 bulk_create_candidates. 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.
bulk_create_candidates is provided by the MCP Ashby Connector MCP server (thnico/mcp-ashby). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP Ashby Connector, 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.
13 MCP Ashby Connector tools catalogued and risk-classified — across an index of 43,000+ MCP servers.