api_run_scenario
Run a prepared scenario once. One approval authorizes every step of that flow: the approval card lists each step method + URL, execution follows the declared order strictly, a failing step stops the rest unless the scenario sets onFailure=continue, and each step keeps its own run record you can i...
This record as markdown: /tools/dutydeck/api-run-scenario.md
What api_run_scenario does on DutyDeck
AI agents invoke api_run_scenario to trigger actions in DutyDeck. 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 api_run_scenario is rated High
api_run_scenario triggers real processes with real consequences. An agent gone sideways doesn't fire it once. It starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs api_run_scenario safely
PolicyLayer is an MCP gateway: it sits between your AI agents and DutyDeck, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For api_run_scenario, this is the rule to start with:
api_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.
The button opens the PolicyLayer dashboard: create your workspace, connect DutyDeck, apply this rule, and every api_run_scenario call is checked against it from then on.
Questions about api_run_scenario
Run a prepared scenario once. One approval authorizes every step of that flow: the approval card lists each step method + URL, execution follows the declared order strictly, a failing step stops the rest unless the scenario sets onFailure=continue, and each step keeps its own run record you can inspect with api_inspect_run. Repeating this call reuses the completed run and never resends. Variables extracted by an earlier step are available to later steps through {{name}}. It is categorised as a Execute tool in the DutyDeck MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the DutyDeck MCP server in PolicyLayer and add a rule for api_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 DutyDeck. Nothing to install.
api_run_scenario is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the api_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.
Set action: deny in the PolicyLayer policy for api_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.
api_run_scenario is provided by the DutyDeck MCP server (taokoplay/DutyDeck). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on DutyDeck, and thousands of servers like it.
Across the catalogue