canvas_run_workflow

从指定 Agent 起点运行一次 bound 可达下游；图片严格受本次上限约束并停在候选验收状态。

SERVERDutyDeck SOURCEtaokoplay/DutyDeck

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/dutydeck/canvas-run-workflow.md

WHAT IT DOES

What canvas_run_workflow does on DutyDeck

AI agents invoke canvas_run_workflow 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.

RISK

Why canvas_run_workflow is rated High

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

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs canvas_run_workflow 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 canvas_run_workflow, this is the rule to start with:

canvas_run_workflow Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "canvas_run_workflow": {
      "limits": [
        {
          "counter": "canvas_run_workflow_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect DutyDeck, apply this rule, and every canvas_run_workflow call is checked against it from then on.

FAQ

Questions about canvas_run_workflow

What does the canvas_run_workflow tool do? +

从指定 Agent 起点运行一次 bound 可达下游；图片严格受本次上限约束并停在候选验收状态。. 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.

How do I enforce a policy on canvas_run_workflow? +

Register the DutyDeck MCP server in PolicyLayer and add a rule for canvas_run_workflow: 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.

What risk level is canvas_run_workflow? +

canvas_run_workflow is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit canvas_run_workflow? +

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

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

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

KEEP EXPLORING

More on DutyDeck, and thousands of servers like it.

This server

All 247 DutyDeck tools → High-risk tools on this server →

Across the catalogue

editor_run_template on 010 Editor →run on 0sec →shortcuts_run on Apple Apps MCP →run_emba_scan on EMBA-MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →