api_prepare_scenario
Prepare a saved scenario (an ordered flow of saved requests) and return its step list: index, method and resolved URL, environment, chosen case and assertion count. No request is sent. Use api_run_scenario on the returned preparedId; the whole flow needs one approval covering exactly this step list.
This record as markdown: /tools/dutydeck/api-prepare-scenario.md
What api_prepare_scenario does on DutyDeck
AI agents call api_prepare_scenario to retrieve information from DutyDeck without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why api_prepare_scenario is rated Low
Even though api_prepare_scenario only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs api_prepare_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_prepare_scenario, this is the rule to start with:
api_prepare_scenario is read-only, so it stays allowed. 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_prepare_scenario call is checked against it from then on.
Questions about api_prepare_scenario
Prepare a saved scenario (an ordered flow of saved requests) and return its step list: index, method and resolved URL, environment, chosen case and assertion count. No request is sent. Use api_run_scenario on the returned preparedId; the whole flow needs one approval covering exactly this step list. It is categorised as a Read tool in the DutyDeck MCP Server, which means it retrieves data without modifying state.
Register the DutyDeck MCP server in PolicyLayer and add a rule for api_prepare_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_prepare_scenario is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the api_prepare_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_prepare_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_prepare_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.
This server
Across the catalogue