New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

model_instance_delete

Delete a model instance.

SERVERKaggle-MCP SOURCE54yyyu/kaggle-mcp
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/54yyyu-kaggle-mcp/model-instance-delete.md

What model_instance_delete does on Kaggle-MCP

AI agents call model_instance_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.

Why model_instance_delete is rated Critical

Deletion operations that cannot be undone fall under the Destructive category. Deleting a model instance permanently removes it from the Kaggle platform, which is a non-recoverable action. The high severity reflects that an AI agent misusing this tool could irretrievably destroy a user's trained models or work products. Confidence is high because the intent is unambiguous.

From the tool's definition Tool name includes 'delete' and description states 'Delete a model instance' — this is an irreversible removal operation.

Questions about model_instance_delete

What does the model_instance_delete tool do? +

Delete a model instance. 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.

How do I enforce a policy on model_instance_delete? +

Register the Kaggle MCP server in PolicyLayer and add a rule for model_instance_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.

What risk level is model_instance_delete? +

model_instance_delete is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit model_instance_delete? +

Yes. Add a rate_limit block to the model_instance_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.

How do I block model_instance_delete completely? +

Set action: deny in the PolicyLayer policy for model_instance_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.

What MCP server provides model_instance_delete? +

model_instance_delete is provided by the Kaggle MCP server (54yyyu/kaggle-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Kaggle, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Kaggle's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.