dataset_register_content · ML Lab MCP: Risk & Policy

WHAT IT DOES

What dataset_register_content does on ML Lab MCP

AI agents use dataset_register_content to create or update resources in ML Lab MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ML Lab MCP environment.

WHY IT NEEDS A POLICY

Why dataset_register_content needs a policy

This tool creates or modifies dataset records in a persistent system (the ML Lab environment), which is a reversible write operation. While it doesn't delete data (not Destructive) or execute arbitrary code (not Execute), it does persist user-provided content into the system's dataset registry.

From the tool's definition Tool name contains 'register' and description states 'Register a dataset from client-provided content', indicating it creates or adds new dataset entries in the ML Lab system.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

dataset_register_content Rate-limited

dataset_register_content 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_register_content": {
      "limits": [
        {
          "counter": "dataset_register_content_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 ML Lab MCP, so you can run agents against it safely.

FAQ

Questions about dataset_register_content

What does the dataset_register_content tool do? +

Register a dataset from client-provided content. It is categorised as a Write tool in the ML Lab 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_register_content? +

Register the ML Lab MCP server in PolicyLayer and add a rule for dataset_register_content: 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 ML Lab MCP. Nothing to install.

What risk level is dataset_register_content? +

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

Can I rate-limit dataset_register_content? +

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

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

dataset_register_content is provided by the ML Lab MCP server (pushpullcommitpush/ml-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.