Delete a model and all its associated storage files.
AI agents call vitrine_delete_model to permanently remove resources in Vitrine MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly deletes data (the model and all associated files), with no undo mechanism implied. Deletion is the canonical destructive operation. High severity because an AI agent misusing this could permanently remove valuable 3D assets and their backups. Confidence is high due to unambiguous language ('delete', 'all', 'storage files').
From the tool's definition Tool name 'vitrine_delete_model' and description explicitly states 'Delete a model and all its associated storage files' — permanent removal of data and storage artifacts.
Attacks that exploit this kind of access
Delete a model and all its associated storage files. It is categorised as a Destructive tool in the Vitrine MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Vitrine MCP Server MCP server in PolicyLayer and add a rule for vitrine_delete_model: 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 Vitrine MCP Server. Nothing to install.
vitrine_delete_model 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 vitrine_delete_model 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 vitrine_delete_model. 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.
vitrine_delete_model is provided by the Vitrine MCP Server MCP server (vitrine3d/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 →