version_restore · Whiteboard MCP: Risk & Policy

WHAT IT DOES

What version_restore does on Whiteboard

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

WHY IT NEEDS A POLICY

Why version_restore needs a policy

This tool modifies canvas state by restoring previous versions, either by reconciling in-place (modifying current canvas) or by writing to a new canvas (creating new data). While it restores rather than creates from scratch, it reversibly alters the diagram state.

From the tool's definition Tool description states 'Restore a saved version' and 'write the past doc as a brand-new canvas'. These actions create or modify canvas state.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

version_restore Rate-limited

version_restore 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": {
    "version_restore": {
      "limits": [
        {
          "counter": "version_restore_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Whiteboard, so you can run agents against it safely.

FAQ

Questions about version_restore

What does the version_restore tool do? +

Restore a saved version. Default = in-place reconcile against the source canvas. Pass targetSlug to instead write the past doc as a brand-new canvas in the same workspace (replaces the deleted checkpoint_restore flow). It is categorised as a Write tool in the Whiteboard MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on version_restore? +

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

What risk level is version_restore? +

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

Can I rate-limit version_restore? +

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

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

version_restore is provided by the Whiteboard MCP server (kamiazya/whiteboard). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.