update_deal
Update a CRM deal. Pass only fields to change; use null for nullable links/fields to clear them.
This record as markdown: /tools/io-favcrm-favcrm/update-deal.md
What update_deal does on FavCRM
AI agents use update_deal 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 |
|---|---|---|---|
name | string | — | Deal name |
stage | object | — | Pipeline stage, or null to clear |
amount | object | — | Deal amount, or null to clear |
dealId | string | Yes | The deal ID |
ownerId | object | — | Owner user/team member ID, or null to clear |
dealType | object | — | Deal type/category, or null to clear |
accountId | object | — | Linked CRM account ID, or null to clear |
contactId | object | — | Linked contact ID, or null to clear |
closingDate | object | — | Expected closing date, or null to clear |
description | object | — | Deal notes or description, or null to clear |
probability | object | — | Win probability, or null to clear |
Parameters from the server's own tool schema.
Why update_deal is rated Medium
This tool modifies existing CRM deal records in a reversible manner (updates can be undone, fields can be changed back). It does not delete data (which would be Destructive), execute arbitrary code (Execute), or transfer funds (Financial).
From the tool's definition Tool description states 'Update a CRM deal' and allows passing 'fields to change' with ability to clear fields using null values, indicating reversible modification of deal data.
Risk signalsHigh parameter count (11 properties)
Attacks that exploit this kind of access
The rule that runs update_deal 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, this is the rule to start with:
update_deal 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 call is checked against it from then on.
Questions about update_deal
Update a CRM deal. Pass only fields to change; use null for nullable links/fields to clear them. 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 accepts 11 parameters: name, stage, amount, dealId, ownerId, dealType, accountId, contactId, closingDate, description, probability. Required: 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: 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 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 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. 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 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