Delete a supplier record (use with caution)
AI agents call quickfile_supplier_delete to permanently remove resources in QuickFile MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deleting supplier records is an irreversible operation that destroys data and cannot be undone. This falls under the Destructive category, which takes precedence over other categories. The 'use with caution' language reinforces the high-risk nature.
From the tool's definition Tool name contains 'delete' and description explicitly states 'Delete a supplier record (use with caution)'. This irreversibly removes data from the accounting system.
Attacks that exploit this kind of access
Delete a supplier record (use with caution). It is categorised as a Destructive tool in the QuickFile MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the QuickFile MCP Server MCP server in PolicyLayer and add a rule for quickfile_supplier_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 QuickFile MCP Server. Nothing to install.
quickfile_supplier_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 quickfile_supplier_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 quickfile_supplier_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.
quickfile_supplier_delete is provided by the QuickFile MCP Server MCP server (marcusquinn/quickfile-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 →