Create a new model.
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.
This tool creates a new model resource on Kaggle, which is a reversible Write operation. It modifies the user's Kaggle account state by adding a new model artifact, but the action can be undone by deletion. Severity is medium because unauthorized model creation could consume account resources, clutter the user's model registry, or be used for spam/abuse, but it does not delete data or commit financial obligations.
From the tool's definition Tool name 'model_create_new' and description 'Create a new model' indicate creation of a new resource on the Kaggle platform.
Attacks that exploit this kind of access
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 (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 →