delete_candidate_tag
AI agents call delete_candidate_tag 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.
Deletion of candidate tags is an irreversible action that removes data associations. While tag deletion is less critical than deleting entire candidate records, it still destroys information that cannot be automatically recovered without audit logs or backups. This meets the Destructive category definition: actions that cannot be undone.
From the tool's definition Tool name 'delete_candidate_tag' directly indicates irreversible deletion operation. Sibling tools include attach_candidate_tags and attach_company_tags (Write operations), establishing pattern where 'delete_*' operations perform destructive actions on the…
Attacks that exploit this kind of access
delete_candidate_tag. 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_candidate_tag: 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_candidate_tag 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_candidate_tag 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_candidate_tag. 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_candidate_tag 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 →