add_scenario_trigger · Dataiku DSS MCP Server MCP

WHAT IT DOES

What add_scenario_trigger does on Dataiku DSS MCP Server

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

This tool creates or modifies a trigger configuration within a Dataiku scenario. Triggers are automation rules that control when scenarios execute, making this a Write operation (reversible modification of scenario metadata). It's medium severity because misconfiguring triggers could cause unintended automated executions of data pipelines, but the action remains reversible (triggers can be modified or removed).

From the tool's definition add_scenario_trigger adds a trigger to a scenario, which modifies scenario configuration. The description indicates creation/modification of scenario automation rules without deletion or irreversibility.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

add_scenario_trigger Rate-limited

add_scenario_trigger 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": {
    "add_scenario_trigger": {
      "limits": [
        {
          "counter": "add_scenario_trigger_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 add_scenario_trigger

What does the add_scenario_trigger tool do? +

Add a trigger to a scenario. 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 add_scenario_trigger? +

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

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

Can I rate-limit add_scenario_trigger? +

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

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

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