update_pipeline_status · CATS MCP Server MCP: Risk & Policy

WHAT IT DOES

What update_pipeline_status does on CATS MCP Server

AI agents use update_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 update_pipeline_status needs a policy

The PUT HTTP method combined with the 'update' verb confirms this tool modifies pipeline status reversibly. It affects recruiting workflow state but does not delete data (hence not Destructive) or execute arbitrary code (hence not Execute).

From the tool's definition Tool name 'update_pipeline_status' and REST method 'PUT /pipelines/{id}/status' indicate modification of existing pipeline state data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_pipeline_status Rate-limited

update_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": {
    "update_pipeline_status": {
      "limits": [
        {
          "counter": "update_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 update_pipeline_status

What does the update_pipeline_status tool do? +

Update pipeline status. PUT /pipelines/{id}/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 update_pipeline_status? +

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

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

Can I rate-limit update_pipeline_status? +

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

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

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