move_elements · Whiteboard MCP: Risk & Policy

WHAT IT DOES

What move_elements does on Whiteboard

AI agents use move_elements 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 move_elements needs a policy

The tool creates or modifies data (element positions) reversibly. Moving elements on a diagram canvas is a non-destructive edit that can be easily undone. While it affects canvas state, it does not delete data (ruling out Destructive), execute arbitrary code (ruling out Execute), or involve financial transactions. The transactional 'all-or-nothing' behavior confirms it is a controlled write operation.

From the tool's definition Tool description states it 'Translate[s] multiple elements' which modifies element positions on the canvas; 'nothing is moved' indicates transactional write semantics without irreversible deletion.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

move_elements Rate-limited

move_elements 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": {
    "move_elements": {
      "limits": [
        {
          "counter": "move_elements_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 move_elements

What does the move_elements tool do? +

Translate multiple elements by the same (dx, dy). All-or-nothing: if any id is missing, nothing is moved. 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 move_elements? +

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

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

Can I rate-limit move_elements? +

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

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

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