add_pipeline_stage · Kommo MCP Server MCP: Risk & Policy

WHAT IT DOES

What add_pipeline_stage does on Kommo MCP Server

AI agents use add_pipeline_stage to create or update resources in Kommo MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Kommo MCP Server environment.

WHY IT NEEDS A POLICY

Why add_pipeline_stage needs a policy

This tool creates a new pipeline stage, which is a reversible modification to CRM configuration. It does not execute arbitrary code, delete data, or move money. While it modifies CRM state, the operation is non-destructive and can typically be undone by removing the stage.

From the tool's definition Tool description: 'Add a new stage (status) to an existing pipeline in Kommo.' The verb 'add' indicates creation of a new configuration entity within a pipeline structure.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

add_pipeline_stage Rate-limited

add_pipeline_stage 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": {
    "add_pipeline_stage": {
      "limits": [
        {
          "counter": "add_pipeline_stage_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 Kommo MCP Server, so you can run agents against it safely.

FAQ

Questions about add_pipeline_stage

What does the add_pipeline_stage tool do? +

Add a new stage (status) to an existing pipeline in Kommo. It is categorised as a Write tool in the Kommo 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 add_pipeline_stage? +

Register the Kommo MCP Server MCP server in PolicyLayer and add a rule for add_pipeline_stage: 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 Kommo MCP Server. Nothing to install.

What risk level is add_pipeline_stage? +

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

Can I rate-limit add_pipeline_stage? +

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

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

add_pipeline_stage is provided by the Kommo MCP Server MCP server (wdavidce/kommo-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.