rename_pipeline_stage · Kommo MCP Server MCP: Risk & Policy

WHAT IT DOES

What rename_pipeline_stage does on Kommo MCP Server

AI agents use rename_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 rename_pipeline_stage needs a policy

This tool modifies existing pipeline stage properties (name, color, sorting, descriptions) but does not delete data or trigger external operations. The changes are reversible and affect only CRM configuration/metadata. While it impacts business workflow structure, the blast radius is limited to pipeline stage customization without data loss or financial consequences.

From the tool's definition Tool description states 'Rename an existing stage/status inside a pipeline, or change its color, sorting, and descriptions' — these are reversible modifications to pipeline configuration metadata.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

rename_pipeline_stage Rate-limited

rename_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": {
    "rename_pipeline_stage": {
      "limits": [
        {
          "counter": "rename_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 rename_pipeline_stage

What does the rename_pipeline_stage tool do? +

Rename an existing stage/status inside a pipeline, or change its color, sorting, and descriptions (tips). 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 rename_pipeline_stage? +

Register the Kommo MCP Server MCP server in PolicyLayer and add a rule for rename_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 rename_pipeline_stage? +

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

Can I rate-limit rename_pipeline_stage? +

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

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

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