mark_deal_lost

Mark a CRM deal as lost. Requires a lost reason.

SERVERFavCRM SOURCEhttps://api.favcrm.io/mcp

Medium RISK CLASS

Category Write

Parameters 22 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-favcrm-favcrm/mark-deal-lost.md

WHAT IT DOES

What mark_deal_lost does on FavCRM

AI agents use mark_deal_lost 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
`dealId`	string	Yes	The deal ID
`reason`	string	Yes	Why the deal was lost

Parameters from the server's own tool schema.

RISK

Why mark_deal_lost is rated Medium

An AI agent can call mark_deal_lost 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

RECOMMENDED RULE

The rule that runs mark_deal_lost 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 mark_deal_lost, this is the rule to start with:

mark_deal_lost Rate-limited

mark_deal_lost 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": {
    "mark_deal_lost": {
      "limits": [
        {
          "counter": "mark_deal_lost_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect FavCRM, apply this rule, and every mark_deal_lost call is checked against it from then on.

FAQ

Questions about mark_deal_lost

What does the mark_deal_lost tool do? +

Mark a CRM deal as lost. Requires a lost reason. 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.

What parameters does mark_deal_lost accept? +

mark_deal_lost accepts 2 parameters: dealId, reason. Required: dealId, reason. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on mark_deal_lost? +

Register the FavCRM MCP server in PolicyLayer and add a rule for mark_deal_lost: 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.

What risk level is mark_deal_lost? +

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

Can I rate-limit mark_deal_lost? +

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

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

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

KEEP EXPLORING

More on FavCRM, and thousands of servers like it.

This server

All 223 FavCRM tools →

Across the catalogue

sms_mark_read on Twilio SMS MCP Server →mark-as-read on Meme MCP Server → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →