Export the whiteboard canvas as a PNG file
AI agents call export_png 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.
This tool reads/exports the current canvas state as a PNG image file. It retrieves data without modifying, deleting, or executing anything. The export is a non-destructive read operation that captures the visual state of the canvas.
From the tool's definition Export the whiteboard canvas as a PNG file
Attacks that exploit this kind of access
Export the whiteboard canvas as a PNG file. 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 export_png: 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.
export_png 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 export_png 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 export_png. 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.
export_png 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 →