canvas_update_image_config

局部更新已有生图节点的提示词、模型、编辑底图、工作流、画幅或上下文；editSourceNodeId 只能选择通过 image.asset -> image.reference 绑定的图片节点，传 null 改用当前节点自身采用图。工作流输入可先保存已知值，运行前必须补齐。分析失败用 preparation 保存错误码、节点/字段和中文原因，修复后传 null 清除。只保存配置，不会自动生图。

SERVERDutyDeck SOURCEtaokoplay/DutyDeck

Medium RISK CLASS

Category Write

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-update-image-config.md

WHAT IT DOES

What canvas_update_image_config does on DutyDeck

AI agents use canvas_update_image_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.

RISK

Why canvas_update_image_config is rated Medium

An AI agent can call canvas_update_image_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

RECOMMENDED RULE

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

canvas_update_image_config Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "canvas_update_image_config": {
      "limits": [
        {
          "counter": "canvas_update_image_config_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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_update_image_config call is checked against it from then on.

FAQ

Questions about canvas_update_image_config

What does the canvas_update_image_config tool do? +

How do I enforce a policy on canvas_update_image_config? +

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

What risk level is canvas_update_image_config? +

canvas_update_image_config is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit canvas_update_image_config? +

Yes. Add a rate_limit block to the canvas_update_image_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.

How do I block canvas_update_image_config completely? +

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

What MCP server provides canvas_update_image_config? +

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

KEEP EXPLORING

More on DutyDeck, and thousands of servers like it.

This server

All 247 DutyDeck tools →

Across the catalogue

aroflo_create_or_update_record on AroFlo MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →