delete_all_drivers
AI agents call delete_all_drivers to permanently remove resources in FleetMind MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly removes all driver records from a delivery dispatch system in a single operation. Misuse would incapacitate the entire fleet—no drivers remain available for deliveries. Blast radius is catastrophic: all pending and future orders cannot be assigned or fulfilled. This is Destructive (not merely Write) because deletion cannot be undone without restoration from backups.
From the tool's definition Tool name 'delete_all_drivers' explicitly indicates irreversible deletion of all driver records. The empty description prevents confirmation of specifics, but the name unambiguously describes a destructive bulk operation.
Attacks that exploit this kind of access
delete_all_drivers. It is categorised as a Destructive tool in the FleetMind MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the FleetMind MCP Server MCP server in PolicyLayer and add a rule for delete_all_drivers: 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 FleetMind MCP Server. Nothing to install.
delete_all_drivers 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_all_drivers 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_all_drivers. 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_all_drivers is provided by the FleetMind MCP Server MCP server (mashrur-rahman-fahim/fleetmind-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 →