Delete a work history entry (permanent).
AI agents call delete_work_history to permanently remove resources in CATS MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Permanent deletion of candidate work history records cannot be undone and represents irreversible data loss. This is a Destructive action, not merely Write (which is reversible). The severity is high because an AI agent with mistaken parameters could permanently delete critical employment records for multiple candidates, damaging recruiting workflows and losing historical data essential to candidate evaluation.
From the tool's definition Tool name 'delete_work_history' explicitly states 'Delete' and description specifies '(permanent)'. This irreversibly removes candidate work history data from the applicant tracking system.
Attacks that exploit this kind of access
Delete a work history entry (permanent). It is categorised as a Destructive tool in the CATS MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the CATS MCP Server MCP server in PolicyLayer and add a rule for delete_work_history: 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.
delete_work_history is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_work_history 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 delete_work_history. 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.
delete_work_history 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 →