This record as markdown: /tools/54yyyu-kaggle-mcp/model-create-new.md
What model_create_new does on Kaggle-MCP
AI agents use model_create_new to create or update resources in Kaggle-MCP, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Kaggle-MCP environment.
Why model_create_new is rated Medium
This tool creates (adds) a new model to Kaggle, which is a reversible write operation. The user can later delete or modify the created model. While model creation is persistent data modification, it does not irreversibly destroy existing data, does not execute arbitrary code on the user's system, and does not involve financial transactions.
From the tool's definition Tool name 'model_create_new' and description 'Create a new model' indicate this creates a new resource in the Kaggle platform.
Attacks that exploit this kind of access
The rule that runs model_create_new safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Kaggle-MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For model_create_new, this is the rule to start with:
model_create_new stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Kaggle-MCP, apply this rule, and every model_create_new call is checked against it from then on.
Questions about model_create_new
Create a new model. It is categorised as a Write tool in the Kaggle-MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Kaggle MCP server in PolicyLayer and add a rule for model_create_new: 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_create_new is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the model_create_new 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_create_new. 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_create_new 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.
This server
Across the catalogue