pixi.tree.highlight
Highlights a node on the canvas. Pass id=null to clear the highlight. Draws nothing while the user has the overlay switched off in the panel (the eye button above the tree).
This record as markdown: /tools/pixi-inspector-mcp/pixi.tree.highlight.md
What pixi.tree.highlight does on Pixi Inspector
AI agents call pixi.tree.highlight 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 |
|---|---|---|---|
id | string | null | Yes | Node id, or null to clear |
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 pixi.tree.highlight is rated Critical
An AI agent that decides to call pixi.tree.highlight 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.
Attacks that exploit this kind of access
The rule that runs pixi.tree.highlight 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 pixi.tree.highlight, this is the rule to start with:
pixi.tree.highlight 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 pixi.tree.highlight call is checked against it from then on.
Questions about pixi.tree.highlight
Highlights a node on the canvas. Pass id=null to clear the highlight. Draws nothing while the user has the overlay switched off in the panel (the eye button above the tree). 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.
pixi.tree.highlight accepts 4 parameters: id, tabId, target, frameId. Required: id. 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 pixi.tree.highlight: 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.
pixi.tree.highlight 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 pixi.tree.highlight 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 pixi.tree.highlight. 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.
pixi.tree.highlight 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