Get candidate details. GET /candidates/{id}
AI agents call get_candidate 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.
This tool retrieves candidate information from the CATS API without modifying, creating, or deleting data. The HTTP GET verb and the 'Get' action in the description confirm it is a simple data retrieval operation with no side effects. Severity is low because reading candidate data poses minimal risk unless the data itself is highly sensitive, but the tool itself has no destructive or harmful capabilities.
From the tool's definition Tool name 'get_candidate' and description 'Get candidate details. GET /candidates/{id}' indicate a read-only retrieval operation using the HTTP GET method.
Attacks that exploit this kind of access
Get candidate details. GET /candidates/{id}. 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: 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 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 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. 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 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 →