Delete a pipeline entry.
AI agents call delete_pipeline 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.
This tool permanently removes a pipeline entry from the CATS system. Pipelines are core recruiting workflow structures that likely contain or reference candidate progression data, job associations, and workflow state. Deletion cannot be undone and represents a destructive action. While not directly financial, the loss of pipeline data could disrupt recruiting operations and candidate tracking.
From the tool's definition Tool name is 'delete_pipeline' with description 'Delete a pipeline entry.' The verb 'delete' explicitly indicates irreversible removal of data.
Attacks that exploit this kind of access
Delete a pipeline entry. 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_pipeline: 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_pipeline 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_pipeline 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_pipeline. 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_pipeline 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 →