Delete a vehicle from the stock permanently ⚠️ WARNING: This action is irreversible! The vehicle will be permanently removed from the stock. When to use: Remove vehicles that are sold, no longer available, or added by mistake Prerequisites: Vehicle ID from list_vehicles or get_vehicle Security: V...
AI agents call delete_vehicle to permanently remove resources in StockSpark MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently deletes data (vehicle records) that cannot be recovered. Destructive category is most appropriate since the action is irreversible and removes inventory records. Severity is high because misuse could delete multiple high-value vehicle inventory records in a dealership system, causing significant business disruption and financial impact.
From the tool's definition Tool description explicitly states 'Delete a vehicle from the stock permanently' and includes warning 'This action is irreversible! The vehicle will be permanently removed from the stock.'
Attacks that exploit this kind of access
Delete a vehicle from the stock permanently ⚠️ WARNING: This action is irreversible! The vehicle will be permanently removed from the stock. When to use: Remove vehicles that are sold, no longer available, or added by mistake Prerequisites: Vehicle ID from list_vehicles or get_vehicle Security: Vehicle info is fetched first for confirmation before deletion. It is categorised as a Destructive tool in the StockSpark MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the StockSpark MCP Server MCP server in PolicyLayer and add a rule for delete_vehicle: 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 StockSpark MCP Server. Nothing to install.
delete_vehicle 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_vehicle 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_vehicle. 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_vehicle is provided by the StockSpark MCP Server MCP server (loukach/stockspark-mcp-poc). 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 →