get_candidate_work_history_item
AI agents call get_candidate_work_history_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.
This tool retrieves candidate work history information without modifying, executing operations on, or deleting data. It functions as a data retrieval operation typical of ATS systems. The lack of description slightly reduces confidence, but the naming convention clearly indicates a read operation.
From the tool's definition Tool name 'get_candidate_work_history_item' indicates retrieval of historical work data for a candidate; no description provided, but the 'get_' prefix and 'work_history' suggest a read-only query operation similar to sibling 'get_' tools in the ATS context.
Attacks that exploit this kind of access
get_candidate_work_history_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_work_history_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_work_history_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_work_history_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_work_history_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_work_history_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 →