Move a deal to cancelled/lost status.
AI agents use crm_cancel_deal to create or update resources in Medicus CRM MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Medicus CRM MCP Server environment.
This tool changes the status of a deal to cancelled or lost. While it modifies deal state, this is a status update (a write operation) rather than a permanent deletion of data — the deal record likely remains in the system. However, cancelling a deal can have significant business consequences (lost revenue, broken workflows), hence high severity.
From the tool's definition Move a deal to cancelled/lost status
Attacks that exploit this kind of access
Move a deal to cancelled/lost status. It is categorised as a Write tool in the Medicus CRM MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Medicus CRM MCP Server MCP server in PolicyLayer and add a rule for crm_cancel_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 Medicus CRM MCP Server. Nothing to install.
crm_cancel_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 crm_cancel_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 crm_cancel_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.
crm_cancel_deal is provided by the Medicus CRM MCP Server MCP server (soundrolling/crmmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →