Capture just a canvas element by selector. Useful for game evidence.
AI agents call browser_screenshot_canvas to retrieve information from DevLab MCP Suite without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool captures visual state of a canvas element for documentation/evidence purposes. It retrieves data (screenshot image) without side effects, modification, or command execution. No code is executed, no data is deleted, and no state changes occur on the device or application. This is clearly a Read operation.
From the tool's definition Tool name and description indicate 'Capture just a canvas element by selector' — a read-only screenshot operation with no modification or execution of game logic.
Attacks that exploit this kind of access
Capture just a canvas element by selector. Useful for game evidence. It is categorised as a Read tool in the DevLab MCP Suite MCP Server, which means it retrieves data without modifying state.
Register the DevLab MCP Suite MCP server in PolicyLayer and add a rule for browser_screenshot_canvas: 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 DevLab MCP Suite. Nothing to install.
browser_screenshot_canvas 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 browser_screenshot_canvas 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 browser_screenshot_canvas. 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.
browser_screenshot_canvas is provided by the DevLab MCP Suite MCP server (tanguito86/devlab-mcp). 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 →