pixi.tree.export
Exports the scene graph to bounded, cycle-safe JSON (id/type/name/childCount, plus optional shallow props). Same lazy philosophy as getTree — depth is hard-capped at 8 (BAD_PARAMS beyond), node count capped by limit (default 5000, max 20000); object refs/textures are never inlined.
This record as markdown: /tools/pixi-inspector-mcp/pixi.tree.export.md
What pixi.tree.export does on Pixi Inspector
AI agents call pixi.tree.export as a supporting operation in Pixi Inspector workflows.
| Parameter | Type | Required | Description |
|---|---|---|---|
depth | integer | — | Levels to export (default 2, hard cap 8) |
limit | integer | — | Max total nodes (default 5000, cap 20000) |
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, |
includeProps | boolean | — | Include shallow transform/visibility props per node |
Parameters from the server's own tool schema.
Why pixi.tree.export is rated Low
Without any rule in front of it, every call an agent makes to pixi.tree.export happens silently: no trail, no cap, no way to know it misbehaved until something breaks downstream.
Attacks that exploit this kind of access
The rule that runs pixi.tree.export 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.export, this is the rule to start with:
pixi.tree.export gets a rate cap, and 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 pixi.tree.export call is checked against it from then on.
Questions about pixi.tree.export
Exports the scene graph to bounded, cycle-safe JSON (id/type/name/childCount, plus optional shallow props). Same lazy philosophy as getTree — depth is hard-capped at 8 (BAD_PARAMS beyond), node count capped by limit (default 5000, max 20000); object refs/textures are never inlined. It is categorised as a Other tool in the Pixi Inspector MCP Server, which means it performs auxiliary operations.
pixi.tree.export accepts 6 parameters: depth, limit, tabId, target, frameId, includeProps. 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.export: 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.export is a Other tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the pixi.tree.export 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.export. 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.export 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