change_pipeline_status · CATS MCP Server MCP: Risk & Policy

WHAT IT DOES

What change_pipeline_status does on CATS MCP Server

AI agents use change_pipeline_status 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.

WHY IT NEEDS A POLICY

Why change_pipeline_status needs a policy

Based on the name, this tool likely modifies the status of a pipeline entry in the applicant tracking system, which is a reversible write operation. The empty description reduces confidence. Given sibling tools like 'change_candidate_thumbnail' and 'change_job_status' are clearly status/attribute updates (Write), this fits the same pattern.

From the tool's definition Tool name 'change_pipeline_status' and server context covering recruiting workflows; description is empty and uninformative.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

change_pipeline_status Rate-limited

change_pipeline_status stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "change_pipeline_status": {
      "limits": [
        {
          "counter": "change_pipeline_status_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches CATS MCP Server, so you can run agents against it safely.

FAQ

Questions about change_pipeline_status

What does the change_pipeline_status tool do? +

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

How do I enforce a policy on change_pipeline_status? +

Register the CATS MCP Server MCP server in PolicyLayer and add a rule for change_pipeline_status: 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 change_pipeline_status? +

change_pipeline_status is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit change_pipeline_status? +

Yes. Add a rate_limit block to the change_pipeline_status 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 change_pipeline_status completely? +

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

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