create_pipeline
AI agents use create_pipeline to create or update resources in CATS MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your CATS MCP Server environment.
Pipeline creation is a reversible write operation that modifies system state by adding a new pipeline configuration. The lack of description reduces confidence slightly, but the pattern of related tools (attach_*_tags, change_*_thumbnail, change_job_status) on the same ATS server confirms this is a write operation. No deletion, financial transaction, or code execution is implied.
From the tool's definition Tool name 'create_pipeline' indicates creation of a new pipeline entity. The context of a recruiting/ATS system suggests this creates a workflow pipeline for job tracking and candidate management.
Attacks that exploit this kind of access
create_pipeline. It is categorised as a Write tool in the CATS MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the CATS MCP Server MCP server in PolicyLayer and add a rule for create_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.
create_pipeline is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_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 create_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.
create_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 →