List whiteboard canvases. Optional filters narrow the output when multiple workspaces / canvases pile up.
AI agents call canvas_list to retrieve information from Whiteboard without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The canvas_list tool performs a read-only operation that retrieves or lists data about whiteboard canvases. There are no side effects, data modifications, deletions, code execution, or financial implications. It is purely informational and falls squarely into the Read category with low severity due to minimal blast radius if misused by an AI agent.
From the tool's definition Tool description states "List whiteboard canvases" with optional filters to narrow output. This is a query operation that retrieves information about existing canvases without modifying, deleting, or executing any operations.
Attacks that exploit this kind of access
List whiteboard canvases. Optional filters narrow the output when multiple workspaces / canvases pile up. It is categorised as a Read tool in the Whiteboard MCP Server, which means it retrieves data without modifying state.
Register the Whiteboard MCP server in PolicyLayer and add a rule for canvas_list: 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.
canvas_list is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the canvas_list 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 canvas_list. 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.
canvas_list 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 →