update_deal_stage
Move a deal to a different pipeline stage.
This record as markdown: /tools/io-favcrm-favcrm/update-deal-stage.md
What update_deal_stage does on FavCRM
AI agents use update_deal_stage to create or update resources in FavCRM, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your FavCRM environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
stage | string | Yes | New pipeline stage. "lead", "new" and "open" are accepted aliases of "discovery". |
dealId | string | Yes | The deal ID |
lostReason | string | — | Required when moving to lost |
probability | string | — | Optional win probability (percent string) |
Parameters from the server's own tool schema.
Why update_deal_stage is rated Medium
An AI agent can call update_deal_stage faster than any human can review: one bad instruction and it creates or modifies resources in FavCRM by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs update_deal_stage safely
PolicyLayer is an MCP gateway: it sits between your AI agents and FavCRM, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For update_deal_stage, this is the rule to start with:
update_deal_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 FavCRM, apply this rule, and every update_deal_stage call is checked against it from then on.
Questions about update_deal_stage
Move a deal to a different pipeline stage. It is categorised as a Write tool in the FavCRM MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
update_deal_stage accepts 4 parameters: stage, dealId, lostReason, probability. Required: stage, dealId. The full parameter table on this page comes from the server's own tool schema.
Register the FavCRM MCP server in PolicyLayer and add a rule for update_deal_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 FavCRM. Nothing to install.
update_deal_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 update_deal_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 update_deal_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.
update_deal_stage is provided by the FavCRM MCP server (https://api.favcrm.io/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on FavCRM, and thousands of servers like it.
This server
Across the catalogue