update_scenario · Dataiku DSS MCP Server MCP: Risk & Policy

WHAT IT DOES

What update_scenario does on Dataiku DSS MCP Server

AI agents use update_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 update_scenario needs a policy

This tool modifies scenario configuration but does not delete data, execute arbitrary code, or move financial resources. It is reversible (settings can be changed again), making it a Write-category risk. Severity is medium because misconfigured scenarios could trigger unintended data operations downstream, but the direct impact is limited to scenario metadata.

From the tool's definition Tool name 'update_scenario' and description 'Update scenario settings' indicate modification of existing configuration data. Scenarios in Dataiku DSS are workflow automation constructs; updating their settings is a reversible write operation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_scenario Rate-limited

update_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": {
    "update_scenario": {
      "limits": [
        {
          "counter": "update_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 update_scenario

What does the update_scenario tool do? +

Update scenario settings. 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 update_scenario? +

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

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

Can I rate-limit update_scenario? +

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

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

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