browser.screenshot

SERVERPixi Inspector SOURCEpixi-inspector-mcp

Low RISK CLASS

Category Other

Parameters 40 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/pixi-inspector-mcp/browser.screenshot.md

WHAT IT DOES

What browser.screenshot does on Pixi Inspector

AI agents call browser.screenshot as a supporting operation in Pixi Inspector workflows.

Parameter	Type	Required	Description
`tabId`	integer	—	Legacy: a bare tab id, resolved inside the browser this session is already working with. Prefer `target`, which is unambiguous across browsers.
`target`	string	—	Drive a specific tab: a target id like "b7a3c1#487" from status/use_target/CHOOSE_TARGET. Omit to use this session's chosen tab (or the only available one). Pas
`frameId`	integer	—	Escape hatch: drive a specific FRAME of the tab (0 is the top frame). Normally unnecessary — the extension picks the frame running the game (canvas owner first,
`includeDataUrl`	boolean	—	Also put the PNG data URL in the text part as `dataUrl` (for scripts that cannot read image parts).

Parameters from the server's own tool schema.

RISK

Why browser.screenshot is rated Low

Without any rule in front of it, every call an agent makes to browser.screenshot happens silently: no trail, no cap, no way to know it misbehaved until something breaks downstream.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs browser.screenshot safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Pixi Inspector, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For browser.screenshot, this is the rule to start with:

browser.screenshot Rate-limited

browser.screenshot gets a rate cap, and everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "browser.screenshot": {
      "limits": [
        {
          "counter": "browser.screenshot_rate",
          "window": "minute",
          "max": 60,
          "scope": "grant"
        }
      ]
    }
  }
}

SET A RULE FOR THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Pixi Inspector, apply this rule, and every browser.screenshot call is checked against it from then on.

FAQ

Questions about browser.screenshot

What does the browser.screenshot tool do? +

Captures the target tab (never another tab) and returns the PNG as an image part, plus a JSON text part with the capture metadata. When the target is the active tab of its window — focused or not — the image is that window's visible area and background is false. When the target is a background tab, it is NOT activated or focused: the image is its last painted frame via a short Chrome debugger attach, with background: true, stale: true and a warning — Chrome does not repaint hidden tabs, so it may be out of date; ask the user to bring the tab to the front for a fresh image. If a background tab gives no image within ~3 s (or the debugger cannot attach, e.g. DevTools is open on it) the call is a PAGE_ERROR whose data carries { tabId, active: false, windowId, reason }. Pass includeDataUrl: true only when a script needs the base64 PNG data URL in the text as dataUrl. It is categorised as a Other tool in the Pixi Inspector MCP Server, which means it performs auxiliary operations.

What parameters does browser.screenshot accept? +

browser.screenshot accepts 4 parameters: tabId, target, frameId, includeDataUrl. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on browser.screenshot? +

Register the Pixi Inspector MCP server in PolicyLayer and add a rule for browser.screenshot: 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 Pixi Inspector. Nothing to install.

What risk level is browser.screenshot? +

browser.screenshot is a Other tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit browser.screenshot? +

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

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

browser.screenshot is provided by the Pixi Inspector MCP server (pixi-inspector-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Pixi Inspector, and thousands of servers like it.

This server

All 63 Pixi Inspector tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Tool risk categories →MCP tool →