browser.targets
Lists the tabs of ONE browser that currently have a live page agent — each as { tabId, url, title, engine, active, lastSeen, enabled }; enabled: true means the user ticked 'Use this tab for MCP' on it. This is a per-browser diagnostic: prefer status, which lists drivable tabs across ALL attached ...
This record as markdown: /tools/pixi-inspector-mcp/browser.targets.md
What browser.targets does on Pixi Inspector
AI agents call browser.targets to retrieve information from Pixi Inspector without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| 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, |
Parameters from the server's own tool schema.
Why browser.targets is rated Low
Even though browser.targets only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs browser.targets 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.targets, this is the rule to start with:
browser.targets is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Pixi Inspector, apply this rule, and every browser.targets call is checked against it from then on.
Questions about browser.targets
Lists the tabs of ONE browser that currently have a live page agent — each as { tabId, url, title, engine, active, lastSeen, enabled }; enabled: true means the user ticked 'Use this tab for MCP' on it. This is a per-browser diagnostic: prefer status, which lists drivable tabs across ALL attached browsers as candidates, each with the target id ("b7a3c1#487") you pass to tools or to use_target. The bare tabId here is only meaningful inside the browser that answered. engine is best-effort and may be null until the app initialises. Needs no chosen tab itself: it asks the browser of target when one is passed (only its browser part is used, and it is not pinned), else this session's browser, else the only attached one. It is categorised as a Read tool in the Pixi Inspector MCP Server, which means it retrieves data without modifying state.
browser.targets accepts 3 parameters: tabId, target, frameId. The full parameter table on this page comes from the server's own tool schema.
Register the Pixi Inspector MCP server in PolicyLayer and add a rule for browser.targets: 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.
browser.targets 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.targets 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.targets. 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.targets 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.
More on Pixi Inspector, and thousands of servers like it.
This server
Across the catalogue