run_scenario · Dataiku DSS MCP Server MCP: Risk & Policy

WHAT IT DOES

What run_scenario does on Dataiku DSS MCP Server

AI agents invoke run_scenario to trigger actions in Dataiku DSS MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why run_scenario needs a policy

This tool triggers execution of a pre-configured scenario, which is an external operation with side effects that depend on the scenario's contents and arguments. It is not merely reading data (Read), not just creating/modifying reversibly (Write), and not destructive by design (Destructive), but rather executing a workflow whose actual impact depends on what the scenario does.

From the tool's definition Tool name 'run_scenario' and description 'Run a scenario manually' indicate execution of a defined workflow/scenario in Dataiku DSS.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

run_scenario Rate-limited

run_scenario stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "run_scenario": {
      "limits": [
        {
          "counter": "run_scenario_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-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 run_scenario

What does the run_scenario tool do? +

Run a scenario manually. It is categorised as a Execute tool in the Dataiku DSS MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on run_scenario? +

Register the Dataiku DSS MCP Server MCP server in PolicyLayer and add a rule for run_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 run_scenario? +

run_scenario is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit run_scenario? +

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

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

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