get_candidate_list_item
AI agents call get_candidate_list_item to retrieve information from CATS MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool appears to fetch or retrieve candidate information from a list without modifying, executing, or deleting data. Despite the empty description reducing confidence slightly, the clear 'get_' nomenclature and sibling tools (which include write, tag attachment, and state-change operations as distinct separate tools) strongly indicate this is a read-only retrieval operation.
From the tool's definition Tool name 'get_candidate_list_item' indicates retrieval of a single candidate record from a list. The 'get_' prefix conventionally denotes read-only query operations.
Attacks that exploit this kind of access
get_candidate_list_item. It is categorised as a Read tool in the CATS MCP Server MCP Server, which means it retrieves data without modifying state.
Register the CATS MCP Server MCP server in PolicyLayer and add a rule for get_candidate_list_item: 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 CATS MCP Server. Nothing to install.
get_candidate_list_item 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 get_candidate_list_item 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 get_candidate_list_item. 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.
get_candidate_list_item is provided by the CATS MCP Server MCP server (vanman2024/cats-mcp-server). 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 →