High Risk →

duplicateWhiteboardElements

Copy-paste existing whiteboard elements — the MCP equivalent of selecting a group and pressing Ctrl/Cmd+D. Clones the given elements (plus their group peers + bound text/labels) with FRESH ids, offsets the copy by dx/dy, and by default groups it into ONE new unit so it moves together. Use it to b...

Part of the Stable Baseline server.

duplicateWhiteboardElements can trigger actions in Stable Baseline, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE STABLE BASELINE →

Free to start. No card required.

AI agents invoke duplicateWhiteboardElements to trigger processes or run actions in Stable Baseline. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.

duplicateWhiteboardElements can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. PolicyLayer enforces rate limits and validates arguments to keep execution within safe bounds.

Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "duplicateWhiteboardElements": {
      "limits": [
        {
          "counter": "duplicatewhiteboardelements_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

See the full Stable Baseline policy for all 184 tools.

Get this rule live on your own Stable Baseline server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY STABLE BASELINE →

View all 184 tools →

These attack patterns abuse exactly the kind of access duplicateWhiteboardElements gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so duplicateWhiteboardElements only ever does what you allow.

SECURE STABLE BASELINE →

Other execute tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.

What does the duplicateWhiteboardElements tool do? +

Copy-paste existing whiteboard elements — the MCP equivalent of selecting a group and pressing Ctrl/Cmd+D. Clones the given elements (plus their group peers + bound text/labels) with FRESH ids, offsets the copy by dx/dy, and by default groups it into ONE new unit so it moves together. Use it to build something once (a labelled stencil frame, a kanban card, a UML class) then stamp out consistent repeats fast — then retext/recolour each copy by its new id (via the returned idMap) with updateWhiteboardScene. Pass groupId to copy a whole group as a unit (e.g. a placed stencil's groupId from its placement result) and/or ids for specific elements. Internal references (group membership, bound text containerId, arrow start/end bindings) are remapped within the copied set; a binding to an element you did NOT copy is dropped. Returns { duplicated, idMap (old id → new id), groupId (the copy's new unit group), elementCount }. Render with getWhiteboardImage afterwards to verify.. It is categorised as a Execute tool in the Stable Baseline MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on duplicateWhiteboardElements? +

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

What risk level is duplicateWhiteboardElements? +

duplicateWhiteboardElements is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit duplicateWhiteboardElements? +

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

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

duplicateWhiteboardElements is provided by the Stable Baseline MCP server (https://api.stablebaseline.io/functions/v1/cloud-serve/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Stable Baseline tool call.

Deterministic rules across all 184 Stable Baseline tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.