Delete a deal from Ploomes CRM by ID. This action is irreversible.
AI agents call ploomes_deals_delete to permanently remove resources in Ploomes — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes deal records from a business CRM system without the ability to undo the action. While not directly financial, deals in a CRM represent business opportunities and commitments that could have significant financial implications. The irreversible nature and potential impact on business operations classify this as Destructive rather than Write.
From the tool's definition Tool description states: 'Delete a deal from Ploomes CRM by ID. This action is irreversible.' The explicit mention of 'delete' and 'irreversible' directly indicates destructive capability.
Attacks that exploit this kind of access
Delete a deal from Ploomes CRM by ID. This action is irreversible. It is categorised as a Destructive tool in the Ploomes MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Ploomes MCP server in PolicyLayer and add a rule for ploomes_deals_delete: 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 Ploomes. Nothing to install.
ploomes_deals_delete 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 ploomes_deals_delete 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 ploomes_deals_delete. 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.
ploomes_deals_delete is provided by the Ploomes MCP server (ploomes-mcp-server). 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 →