dataset_update_metadata · Kaggle- MCP: Risk & Policy

WHAT IT DOES

What dataset_update_metadata does on Kaggle-MCP

AI agents use dataset_update_metadata 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 IT NEEDS A POLICY

Why dataset_update_metadata needs a policy

This tool modifies dataset metadata on Kaggle, which is a reversible write operation. It does not delete data (Destructive), execute code (Execute), involve financial transactions (Financial), or retrieve data without side effects (Read).

From the tool's definition Tool name is 'dataset_update_metadata' and description states 'Update dataset metadata.' The verb 'update' indicates modification of existing data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

dataset_update_metadata Rate-limited

dataset_update_metadata 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "dataset_update_metadata": {
      "limits": [
        {
          "counter": "dataset_update_metadata_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Kaggle-MCP, so you can run agents against it safely.

FAQ

Questions about dataset_update_metadata

What does the dataset_update_metadata tool do? +

Update dataset metadata. 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.

How do I enforce a policy on dataset_update_metadata? +

Register the Kaggle- MCP server in PolicyLayer and add a rule for dataset_update_metadata: 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 dataset_update_metadata? +

dataset_update_metadata is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit dataset_update_metadata? +

Yes. Add a rate_limit block to the dataset_update_metadata 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 dataset_update_metadata completely? +

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

dataset_update_metadata 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.