remove_scenario_trigger · Dataiku DSS MCP Server MCP

WHAT IT DOES

What remove_scenario_trigger does on Dataiku DSS MCP Server

AI agents call remove_scenario_trigger to permanently remove resources in Dataiku DSS MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

WHY IT NEEDS A POLICY

Why remove_scenario_trigger needs a policy

Removing a trigger is an irreversible destructive action; once deleted, the trigger configuration is gone and any automation it provided is lost. Blast radius is medium since it affects scenario scheduling/automation but doesn't delete data.

From the tool's definition 'Remove a trigger from a scenario' — permanently removes a trigger configuration

Attacks that exploit this kind of access

Questions about remove_scenario_trigger

What does the remove_scenario_trigger tool do? +

Remove a trigger from a scenario. It is categorised as a Destructive tool in the Dataiku DSS MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on remove_scenario_trigger? +

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

remove_scenario_trigger is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit remove_scenario_trigger? +

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

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

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