[FacturaHub] Delete a vendor/supplier.
AI agents call delete_vendor to permanently remove resources in FacturaHub MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deletion of vendor records is a destructive action that cannot be undone and results in permanent loss of supplier data. While not directly financial, this could impact business operations and vendor relationships. The operation is irreversible, making it more severe than Write operations. High severity due to potential business disruption from loss of critical vendor information.
From the tool's definition Tool name 'delete_vendor' combined with description 'Delete a vendor/supplier' explicitly performs an irreversible deletion operation on supplier records.
Attacks that exploit this kind of access
[FacturaHub] Delete a vendor/supplier. It is categorised as a Destructive tool in the FacturaHub MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the FacturaHub MCP Server MCP server in PolicyLayer and add a rule for delete_vendor: 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 FacturaHub MCP Server. Nothing to install.
delete_vendor 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 delete_vendor 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 delete_vendor. 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.
delete_vendor is provided by the FacturaHub MCP Server MCP server (santy1422/facturahub-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 →