Delete a model instance version.
AI agents call model_instance_version_delete to permanently remove resources in Kaggle-MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool performs an irreversible deletion of a model instance version, which cannot be undone. This fits the Destructive category definition. The severity is high because deletion of a user's model version could cause significant disruption, though the blast radius is somewhat limited to the specific version rather than broader system impact.
From the tool's definition Tool name explicitly contains 'delete' and description states 'Delete a model instance version.' This is an irreversible operation that removes data from the Kaggle platform.
Attacks that exploit this kind of access
Delete a model instance version. It is categorised as a Destructive tool in the Kaggle-MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Kaggle- MCP server in PolicyLayer and add a rule for model_instance_version_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 Kaggle-MCP. Nothing to install.
model_instance_version_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 model_instance_version_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 model_instance_version_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.
model_instance_version_delete is provided by the Kaggle- MCP server (realbytecode/kaggle-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 →