canvas_run_agent
显式运行单个 Canvas Agent 并等待终态；不会自动运行下游节点或启动图片任务。专业审核用 reviewScope 明确整图或指定节点，返回 reviewCoverage 数据覆盖；首次导演规划可用 positionBeforeNodeIds 将该Agent移到制作节点前方，只改位置不加边。
This record as markdown: /tools/dutydeck/canvas-run-agent.md
What canvas_run_agent does on DutyDeck
AI agents invoke canvas_run_agent 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 canvas_run_agent is rated High
canvas_run_agent 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
The rule that runs canvas_run_agent 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_agent, this is the rule to start with:
canvas_run_agent 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 canvas_run_agent call is checked against it from then on.
Questions about canvas_run_agent
显式运行单个 Canvas Agent 并等待终态；不会自动运行下游节点或启动图片任务。专业审核用 reviewScope 明确整图或指定节点，返回 reviewCoverage 数据覆盖；首次导演规划可用 positionBeforeNodeIds 将该Agent移到制作节点前方，只改位置不加边。. 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 canvas_run_agent: 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.
canvas_run_agent 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 canvas_run_agent 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 canvas_run_agent. 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.
canvas_run_agent 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