use_target
Pins the tab every later page/browser/cdp call in THIS session acts on, and remembers it until the tab goes away or you change it. Call this after a CHOOSE_TARGET error: show the listed candidates to the user, ask which one, then pass its target id (e.g. "b7a3c1#487" — never invent one; take it f...
This record as markdown: /tools/pixi-inspector-mcp/use-target.md
What use_target does on Pixi Inspector
AI agents call use_target to permanently remove resources in Pixi Inspector, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
clear | boolean | — | Forget the current choice instead of setting one. |
target | string | — | Target id from status/CHOOSE_TARGET, e.g. "b7a3c1#487" (<browser>#<tabId>). |
Parameters from the server's own tool schema.
Why use_target is rated Critical
An AI agent that decides to call use_target doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Pixi Inspector is gone. There is no undo for destructive operations.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs use_target 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 use_target, this is the rule to start with:
use_target is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Pixi Inspector, apply this rule, and every use_target call is checked against it from then on.
Questions about use_target
Pins the tab every later page/browser/cdp call in THIS session acts on, and remembers it until the tab goes away or you change it. Call this after a CHOOSE_TARGET error: show the listed candidates to the user, ask which one, then pass its target id (e.g. "b7a3c1#487" — never invent one; take it from the error or from status). You do NOT need this when only one tab is available: that tab is used automatically. Pass no argument to read the current choice, or clear: true to forget it. It is categorised as a Destructive tool in the Pixi Inspector MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
use_target accepts 2 parameters: clear, target. 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 use_target: 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.
use_target is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the use_target 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 use_target. 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.
use_target 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.
Across the catalogue