List all notes for a candidate. Returns note content, author, and date.
AI agents call candidate_list_notes to retrieve information from Ashby MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a retrieval operation on candidate notes—it lists and returns data (note content, author, date) without creating, modifying, deleting, or executing any external operations. It has no side effects and poses minimal security risk beyond potential information disclosure, which is typical of read operations in HR systems.
From the tool's definition Tool name 'candidate_list_notes' and description 'List all notes for a candidate. Returns note content, author, and date.' indicate a read-only query operation that retrieves existing data without modification.
Documented attack patterns abuse exactly the kind of access candidate_list_notes gives an agent:
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_list_notes:
{
"version": "1",
"default": "deny",
"tools": {
"candidate_list_notes": {}
}
} candidate_list_notes is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List all notes for a candidate. Returns note content, author, and date. It is categorised as a Read tool in the Ashby MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Ashby MCP Server MCP server in PolicyLayer and add a rule for candidate_list_notes: 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.
candidate_list_notes 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 candidate_list_notes 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 candidate_list_notes. 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.
candidate_list_notes 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.
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.
Free to start. No card required.
21 Ashby MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.