pixi.stats
Everything the panel's Statistics tab shows, in one call. frame: FPS, frame time avg/max, draw calls avg/last, renderer type, resolution, ticker, plus the FULL 300-sample histories (window says how many the ring holds, samples how many are filled) — and visible/hooked/glHooked/foreignHook, which ...
This record as markdown: /tools/pixi-inspector-mcp/pixi.stats.md
What pixi.stats does on Pixi Inspector
AI agents invoke pixi.stats to trigger actions in Pixi Inspector. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| 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, |
sections | array | — | Which sections to collect. Omit for all three. Use ["frame"] when polling, so the scene walk is skipped. |
Parameters from the server's own tool schema.
Why pixi.stats is rated High
pixi.stats triggers real processes with real consequences. An agent gone sideways doesn't fire it once. It starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs pixi.stats 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.stats, this is the rule to start with:
pixi.stats stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. 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.stats call is checked against it from then on.
Questions about pixi.stats
Everything the panel's Statistics tab shows, in one call. frame: FPS, frame time avg/max, draw calls avg/last, renderer type, resolution, ticker, plus the FULL 300-sample histories (window says how many the ring holds, samples how many are filled) — and visible/hooked/glHooked/foreignHook, which say WHY a counter is null (a hidden tab renders no frames; foreignHook means an older extension build instrumented this renderer and the page needs a reload; Phaser has no draw-call instrumentation). scene: node census (containers/leaves, counts by type) and the cost drivers — nodes with filters, masks or cacheAsTexture, distinct texture sources against the GPU's MAX_TEXTURE_IMAGE_UNITS, textures over 4096 px, blend modes, interactive nodes, approximate texture memory (w*h*4) and the texture GC settings (whose unit matters: v8 counts ms, v6/v7 counts FRAMES). page: TTFB/FCP/LCP, requests and bytes by initiator type, JS heap (runtime.heap, Chrome-only, page-wide — not GPU memory) with its own runtime.heapHistoryMB ring sampled every 250 ms (sampling starts on the first page read and stops after 5 min without one, so a call after a pause returns a short history), long tasks, INP, CLS, GPU strings and WebGL limits, hardwareConcurrency/deviceMemory. Long tasks, INP and CLS are counted SINCE OBSERVATION STARTED, reported as observedForMs — not for the whole session. Pass sections to skip work: the scene census walks the whole tree. It is categorised as a Execute tool in the Pixi Inspector MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
pixi.stats accepts 4 parameters: tabId, target, frameId, sections. 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.stats: 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.stats is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the pixi.stats 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.stats. 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.stats 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