Merge entries into the workspace color palette and return the resulting palette.
AI agents use palette_set 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.
This tool modifies the color palette of an Excalidraw diagram by adding or updating color entries. It is a reversible write operation (colors can be changed or removed later) with minimal blast radius - color palette changes do not affect critical data, financial systems, or enable execution of external commands.
From the tool's definition Tool description states "Merge entries into the workspace color palette" - a modification operation. The term "Merge" indicates data is being created or modified within the palette state, not retrieved or deleted.
Attacks that exploit this kind of access
Merge entries into the workspace color palette and return the resulting palette. 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.
Register the Whiteboard MCP server in PolicyLayer and add a rule for palette_set: 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.
palette_set is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the palette_set 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.
Set action: deny in the PolicyLayer policy for palette_set. 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.
palette_set 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →