create_deal
Create a CRM sales pipeline deal, optionally linked to a customer account and contact.
This record as markdown: /tools/io-favcrm-favcrm/create-deal.md
What create_deal does on FavCRM
AI agents use create_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 | Yes | Deal name |
stage | object | — | Pipeline stage |
amount | object | — | Deal amount |
ownerId | object | — | Owner user/team member ID |
dealType | object | — | Deal type/category |
accountId | object | — | Linked CRM account ID |
contactId | object | — | Linked contact ID |
closingDate | object | — | Expected closing date |
description | object | — | Deal notes or description |
probability | object | — | Win probability, e.g. 25 |
Parameters from the server's own tool schema.
Why create_deal is rated Medium
This tool creates new deal records in the sales pipeline, which is a reversible write operation. It does not execute arbitrary code, trigger external operations with unpredictable side effects, delete data, or move money. The blast radius is moderate—a compromised agent could create spurious deals that clutter the pipeline or mislead sales reporting, but these can be deleted or corrected.
From the tool's definition Tool name 'create_deal' and description 'Create a CRM sales pipeline deal' explicitly indicates creation of new data in the CRM system.
Risk signalsHigh parameter count (10 properties)
Attacks that exploit this kind of access
The rule that runs create_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 create_deal, this is the rule to start with:
create_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 create_deal call is checked against it from then on.
Questions about create_deal
Create a CRM sales pipeline deal, optionally linked to a customer account and contact. 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.
create_deal accepts 10 parameters: name, stage, amount, ownerId, dealType, accountId, contactId, closingDate, description, probability. Required: name. 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 create_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.
create_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 create_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 create_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.
create_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