This record as markdown: /tools/abraflexi/contact-delete.md
What contact_delete does on AbraFlexi
AI agents call contact_delete to permanently remove resources in AbraFlexi, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why contact_delete is rated Critical
This tool permanently removes contact or company records from the AbraFlexi system. Deletion is irreversible and cannot be undone, making it Destructive. The severity is high because loss of contact/company records can disrupt business operations, customer relationships, and data integrity, though the impact is typically scoped to individual records rather than system-wide (which would be critical).
From the tool's definition Tool name 'contact_delete' and description 'Delete a contact/company from AbraFlexi' explicitly indicate irreversible deletion of data.
Attacks that exploit this kind of access
The rule that runs contact_delete safely
PolicyLayer is an MCP gateway: it sits between your AI agents and AbraFlexi, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For contact_delete, this is the rule to start with:
contact_delete 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 AbraFlexi, apply this rule, and every contact_delete call is checked against it from then on.
Questions about contact_delete
Delete a contact/company from AbraFlexi. It is categorised as a Destructive tool in the AbraFlexi MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the AbraFlexi MCP server in PolicyLayer and add a rule for contact_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 AbraFlexi. Nothing to install.
contact_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 contact_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 contact_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.
contact_delete is provided by the AbraFlexi MCP server (abraflexi-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on AbraFlexi, and thousands of servers like it.
Across the catalogue