pipedrive_update_stage
Update an existing stage. Provide the stage id and any fields to change. Set pipeline_id to move the stage to another pipeline.
This record as markdown: /tools/ckalima-pipedrive-mcp-server/pipedrive-update-stage.md
What pipedrive_update_stage does on Pipedrive MCP Server
AI agents use pipedrive_update_stage to create or update resources in Pipedrive MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Pipedrive MCP Server environment.
Why pipedrive_update_stage is rated Medium
This tool modifies existing CRM pipeline stage configuration. While reversible (Write category, not Destructive), it impacts business process workflows that sales teams depend on. Misuse could disrupt deal pipeline organization, affecting multiple users and deals. However, the change is not irreversible and does not commit financial transactions, placing it at medium severity rather than high.
From the tool's definition Tool description states 'Update an existing stage' and allows modification of stage fields and pipeline reassignment ('Set pipeline_id to move the stage to another pipeline'). The action is reversible—updated stages can be modified again.
Attacks that exploit this kind of access
The rule that runs pipedrive_update_stage safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Pipedrive MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For pipedrive_update_stage, this is the rule to start with:
pipedrive_update_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.
The button opens the PolicyLayer dashboard: create your workspace, connect Pipedrive MCP Server, apply this rule, and every pipedrive_update_stage call is checked against it from then on.
Questions about pipedrive_update_stage
Update an existing stage. Provide the stage id and any fields to change. Set pipeline_id to move the stage to another pipeline. It is categorised as a Write tool in the Pipedrive MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Pipedrive MCP Server MCP server in PolicyLayer and add a rule for pipedrive_update_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 Pipedrive MCP Server. Nothing to install.
pipedrive_update_stage 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 pipedrive_update_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.
Set action: deny in the PolicyLayer policy for pipedrive_update_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.
pipedrive_update_stage is provided by the Pipedrive MCP Server MCP server (ckalima/pipedrive-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Pipedrive MCP Server, and thousands of servers like it.
This server
Across the catalogue