canvas_update_artifact

更新已有文档、WebView 正文或图片提示词；图片只保存配置，不会生图。用户要求立即生图时必须另行调用 canvas_run_nodes。初始正文 revision 0 可直接更新；版本冲突时先 canvas_read 复读当前画布 revision 与节点正文，合并新改动后再提交，不能把图版本过期诊断为正文损坏。

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-artifact.md

WHAT IT DOES

What canvas_update_artifact does on DutyDeck

AI agents use canvas_update_artifact 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_artifact is rated Medium

An AI agent can call canvas_update_artifact 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_artifact 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_artifact, this is the rule to start with:

canvas_update_artifact Rate-limited

canvas_update_artifact 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_artifact": {
      "limits": [
        {
          "counter": "canvas_update_artifact_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_artifact call is checked against it from then on.

FAQ

Questions about canvas_update_artifact

What does the canvas_update_artifact tool do? +

How do I enforce a policy on canvas_update_artifact? +

Register the DutyDeck MCP server in PolicyLayer and add a rule for canvas_update_artifact: 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_artifact? +

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

Can I rate-limit canvas_update_artifact? +

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

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

canvas_update_artifact 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 →