clone_scenario · Dataiku DSS MCP Server MCP: Risk & Policy

WHAT IT DOES

What clone_scenario does on Dataiku DSS MCP Server

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

WHY IT NEEDS A POLICY

Why clone_scenario needs a policy

Cloning creates a new copy of an existing scenario, which is a reversible write operation. It does not delete or overwrite existing data, execute code, or involve financial transactions. The 'with modifications' aspect suggests it may alter the cloned copy, but the original remains intact. Severity is medium because scenarios can trigger complex workflows in Dataiku DSS.

From the tool's definition Clone an existing scenario with modifications

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

clone_scenario Rate-limited

clone_scenario 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": {
    "clone_scenario": {
      "limits": [
        {
          "counter": "clone_scenario_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 Dataiku DSS MCP Server, so you can run agents against it safely.

FAQ

Questions about clone_scenario

What does the clone_scenario tool do? +

Clone an existing scenario with modifications. It is categorised as a Write tool in the Dataiku DSS MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on clone_scenario? +

Register the Dataiku DSS MCP Server MCP server in PolicyLayer and add a rule for clone_scenario: 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 Dataiku DSS MCP Server. Nothing to install.

What risk level is clone_scenario? +

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

Can I rate-limit clone_scenario? +

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

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

clone_scenario is provided by the Dataiku DSS MCP Server MCP server (steven0lisa/mcp-dataiku). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.