AI agents call candidate_tag_list to retrieve information from Ashby MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns existing tag data without modifying, executing code, deleting, or affecting financial systems. It is a straightforward read operation with minimal blast radius if misused by an AI agent.
From the tool's definition Tool description states 'List all available candidate tags' — a retrieval operation with no side effects.
Attacks that exploit this kind of access
List all available candidate tags. It is categorised as a Read tool in the Ashby MCP MCP Server, which means it retrieves data without modifying state.
Register the Ashby MCP server in PolicyLayer and add a rule for candidate_tag_list: 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.
candidate_tag_list 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_tag_list 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_tag_list. 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_tag_list 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.
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 →