candidate_info

THE RISK

Low Risk

Why candidate_info needs a policy

This tool retrieves candidate information without modifying data, executing code, or triggering external operations. It is a straightforward query function that falls squarely into the Read category with low severity due to limited blast radius if misused by an AI agent.

From the tool's definition Tool name 'candidate_info' and description 'Get details of a single candidate by ID' indicate a retrieval operation with no modification or side effects.

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

POLICY

How to control candidate_info

PolicyLayer is an MCP gateway — it sits between your AI agents and Ashby MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for candidate_info:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "candidate_info": {}
  }
}

candidate_info is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register Ashby MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Ashby MCP Server tools

Write application_change_stage Move an application to a different interview stage. Write application_create Create an application linking a candidate to a job. Write candidate_add_tag Add a tag to a candidate. This is a WRITE operation. Write candidate_create Create a new candidate in Ashby. Only Write candidate_create_note Add a note to a candidate. Supports HTML formatting in the note body. Read application_info Get full details for a single application by ID. Returns candidate, job, Read application_list List applications (candidates in a hiring pipeline). Filter by jobId to see Read candidate_full_profile Get a complete view of a candidate: their info, all applications (with job

All 21 Ashby MCP Server tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about candidate_info

What does the candidate_info tool do? +

Get details of a single candidate by ID. For a complete profile including. It is categorised as a Read tool in the Ashby MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on candidate_info? +

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

What risk level is candidate_info? +

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

Can I rate-limit candidate_info? +

Yes. Add a rate_limit block to the candidate_info 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_info completely? +

Set action: deny in the PolicyLayer policy for candidate_info. 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_info? +

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

Enforce policy on every Ashby MCP Server tool call.

Start from Ashby MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →