dataset_create_version
A write tool on the Kaggle- MCP server.
This record as markdown: /tools/54yyyu-kaggle-mcp/dataset-create-version.md
What dataset_create_version does on Kaggle-MCP
AI agents use dataset_create_version 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 dataset_create_version is rated Medium
Creating a dataset version is a reversible Write operation—it creates or modifies dataset metadata on Kaggle without permanently destroying data. While it could impact other users relying on the dataset, the action is not destructive (prior versions remain intact), not financial, and not code execution.
From the tool's definition Tool name 'dataset_create_version' indicates creation of a new version of a dataset, which modifies dataset metadata and structure on Kaggle. The description is empty, limiting specificity.
Attacks that exploit this kind of access
The rule that runs dataset_create_version 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 dataset_create_version, this is the rule to start with:
dataset_create_version 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 dataset_create_version call is checked against it from then on.
Questions about dataset_create_version
dataset_create_version is a write tool on the Kaggle MCP server. 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 dataset_create_version: 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.
dataset_create_version 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 dataset_create_version 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 dataset_create_version. 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.
dataset_create_version 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