canvas_update_media_config
以配置 revision 保存音视频卡片；workflow 固定公共或当前项目的工作流版本和连接，profile 仅兼容旧预设且两者互斥。先用 media_list_workflows/media_inspect_workflow 读取真实输入输出，inputs 可先只填已知值，缺失项留待配置，运行前必须补齐。省略字段保留现状；更换工作流时同时提供新的 inputs/outputs。outputs 必须按工作流输出顺序填写 key、mediaKind、role、order；绑定工作流时不能为空，恰好一个 primary 且类型匹配当前卡片，order 从 0 连续递增。分析失败用 pre...
This record as markdown: /tools/dutydeck/canvas-update-media-config.md
What canvas_update_media_config does on DutyDeck
AI agents use canvas_update_media_config to create or update resources in DutyDeck, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your DutyDeck environment.
Why canvas_update_media_config is rated Medium
An AI agent can call canvas_update_media_config faster than any human can review: one bad instruction and it creates or modifies resources in DutyDeck by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs canvas_update_media_config 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_update_media_config, this is the rule to start with:
canvas_update_media_config stays usable, but capped: an agent stuck in a loop can't make hundreds of changes 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_update_media_config call is checked against it from then on.
Questions about canvas_update_media_config
以配置 revision 保存音视频卡片；workflow 固定公共或当前项目的工作流版本和连接，profile 仅兼容旧预设且两者互斥。先用 media_list_workflows/media_inspect_workflow 读取真实输入输出，inputs 可先只填已知值，缺失项留待配置，运行前必须补齐。省略字段保留现状；更换工作流时同时提供新的 inputs/outputs。outputs 必须按工作流输出顺序填写 key、mediaKind、role、order；绑定工作流时不能为空，恰好一个 primary 且类型匹配当前卡片，order 从 0 连续递增。分析失败用 preparation 保存错误码、节点/字段和中文原因，修复后传 null 清除。回执 connectionStatus 会列出缺失真实图边；为 missingEdges 分配稳定 id 后，用 canvas_apply_changes 的 upsert-edges 一次补齐。保存不提交生成。. It is categorised as a Write tool in the DutyDeck MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the DutyDeck MCP server in PolicyLayer and add a rule for canvas_update_media_config: 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_update_media_config is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the canvas_update_media_config 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_update_media_config. 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_update_media_config 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