remove_deal_prospect
Unlink a contact (prospect_id) from a deal. A won deal must keep at least one contact. Returns {success: true}.
This record as markdown: /tools/digital-crew-technologies-max-mcp-server/remove-deal-prospect.md
What remove_deal_prospect does on Max MCP Server
AI agents call remove_deal_prospect to permanently remove resources in Max MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why remove_deal_prospect is rated Critical
Removes deal-prospect association irreversibly; cannot be undone without manual intervention.
From the tool's definition Unlink a contact from a deal; irreversible relationship removal.
Attacks that exploit this kind of access
The rule that runs remove_deal_prospect safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Max MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For remove_deal_prospect, this is the rule to start with:
remove_deal_prospect is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Max MCP Server, apply this rule, and every remove_deal_prospect call is checked against it from then on.
Questions about remove_deal_prospect
Unlink a contact (prospect_id) from a deal. A won deal must keep at least one contact. Returns {success: true}. It is categorised as a Destructive tool in the Max MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Max MCP Server MCP server in PolicyLayer and add a rule for remove_deal_prospect: 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 Max MCP Server. Nothing to install.
remove_deal_prospect is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the remove_deal_prospect 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 remove_deal_prospect. 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.
remove_deal_prospect is provided by the Max MCP Server MCP server (digital-crew-technologies/max-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Max MCP Server, and thousands of servers like it.
Across the catalogue