Remove um deal do CRM
AI agents call kinbox_delete_deal to permanently remove resources in Kinbox — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes deal data from the CRM system without the ability to undo the action. Deletion of business records (deals/opportunities) constitutes a destructive operation with potentially significant business impact, as deals represent revenue opportunities and sales pipeline. While not as critical as financial transactions, the loss of deal data can harm business operations and reporting.
From the tool's definition Tool name 'kinbox_delete_deal' and description 'Remove um deal do CRM' (Remove a deal from the CRM) indicate irreversible deletion of deal records.
Attacks that exploit this kind of access
Remove um deal do CRM. It is categorised as a Destructive tool in the Kinbox MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Kinbox MCP server in PolicyLayer and add a rule for kinbox_delete_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 Kinbox. Nothing to install.
kinbox_delete_deal 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 kinbox_delete_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 kinbox_delete_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.
kinbox_delete_deal is provided by the Kinbox MCP server (vergamini65-boop/kinbox-mcp). 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 →