delete_candidate_list_item

delete_candidate_list_item

Server CATS MCP Server vanman2024/cats-mcp-server
Category Destructive
Risk class Critical
Parameters 00 required

What delete_candidate_list_item does on CATS MCP Server

AI agents call delete_candidate_list_item 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.

Why delete_candidate_list_item needs a policy

The 'delete' verb indicates an irreversible destructive action. Within a recruiting workflow system managing candidate data, deletion of candidate-related items would be a permanent, non-recoverable operation affecting business-critical information. This is the most severe category. Confidence is slightly reduced (0.85 vs 1.0) due to empty description, but the tool name alone clearly indicates destructive intent.

From the tool's definition Tool name 'delete_candidate_list_item' contains 'delete' which indicates irreversible removal of data. The empty description prevents confirmation of exact semantics, but in an applicant tracking system context, deletion of candidate records or list items…

Questions about delete_candidate_list_item

What does the delete_candidate_list_item tool do? +

delete_candidate_list_item. 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.

How do I enforce a policy on delete_candidate_list_item? +

Register the CATS MCP Server MCP server in PolicyLayer and add a rule for delete_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.

What risk level is delete_candidate_list_item? +

delete_candidate_list_item is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete_candidate_list_item? +

Yes. Add a rate_limit block to the delete_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.

How do I block delete_candidate_list_item completely? +

Set action: deny in the PolicyLayer policy for delete_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.

What MCP server provides delete_candidate_list_item? +

delete_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.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.