canvas_checkpoint

Save a named checkpoint of the current canvas state.

SERVERCoWork OS SOURCECoWork-OS/CoWork-OS

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/cowork-os/canvas-checkpoint.md

WHAT IT DOES

What canvas_checkpoint does on CoWork OS

AI agents use canvas_checkpoint to create or update resources in CoWork OS, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your CoWork OS environment.

RISK

Why canvas_checkpoint is rated Medium

Saving a checkpoint is a write operation as it creates new data (a named snapshot). It is reversible and localized to canvas state management with minimal blast radius, hence low severity. The description is clear and direct, supporting high confidence.

From the tool's definition Tool description explicitly states 'Save a named checkpoint' — this is a create operation that stores a canvas state snapshot. It is reversible (checkpoints can be overwritten or deleted) and has no destructive or external side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs canvas_checkpoint safely

PolicyLayer is an MCP gateway: it sits between your AI agents and CoWork OS, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For canvas_checkpoint, this is the rule to start with:

canvas_checkpoint Rate-limited

canvas_checkpoint 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_checkpoint": {
      "limits": [
        {
          "counter": "canvas_checkpoint_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 CoWork OS, apply this rule, and every canvas_checkpoint call is checked against it from then on.

FAQ

Questions about canvas_checkpoint

What does the canvas_checkpoint tool do? +

Save a named checkpoint of the current canvas state. It is categorised as a Write tool in the CoWork OS MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on canvas_checkpoint? +

Register the CoWork OS MCP server in PolicyLayer and add a rule for canvas_checkpoint: 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 CoWork OS. Nothing to install.

What risk level is canvas_checkpoint? +

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

Can I rate-limit canvas_checkpoint? +

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

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

canvas_checkpoint is provided by the CoWork OS MCP server (CoWork-OS/CoWork-OS). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on CoWork OS, and thousands of servers like it.

This server

All 342 CoWork OS tools →

Across the catalogue

team_manager_record_checkpoint on Team Manager MCP → The MCP Attack Database →

Guides

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