candidate_create · Ashby MCP: Risk & Policy

WHAT IT DOES

What candidate_create does on Ashby MCP

AI agents use candidate_create to create or update resources in Ashby MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ashby MCP environment.

WHY IT NEEDS A POLICY

Why candidate_create needs a policy

This tool creates new records in the recruiting system. While reversible (candidates can be deleted or records removed), creating candidate records commits data that may trigger downstream workflows, communications, or other recruiting processes. The blast radius is moderate—erroneous candidate creation could cause recruiting delays or process confusion, but does not delete data or move money.

From the tool's definition Tool name 'candidate_create' and description 'Create a new candidate' directly indicate data creation. Ashby is a recruiting platform where candidates are core entities representing potential job applicants.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

candidate_create Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "candidate_create": {
      "limits": [
        {
          "counter": "candidate_create_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Ashby MCP, so you can run agents against it safely.

FAQ

Questions about candidate_create

What does the candidate_create tool do? +

Create a new candidate. It is categorised as a Write tool in the Ashby MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on candidate_create? +

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

What risk level is candidate_create? +

candidate_create is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit candidate_create? +

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

How do I block candidate_create completely? +

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

What MCP server provides candidate_create? +

candidate_create is provided by the Ashby MCP server (jaketeagle/ashby-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.