pixi.app.renderStats
Render-loop counters sampled by hooking the renderer (rolling average over the last frames): draw calls, render time, measured FPS, container/leaf counts. The first call installs the hook — call again after a few frames for populated samples.
This record as markdown: /tools/pixi-inspector-mcp/pixi.app.renderstats.md
What pixi.app.renderStats does on Pixi Inspector
AI agents call pixi.app.renderStats as a supporting operation in Pixi Inspector workflows.
| 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 pixi.app.renderStats is rated Low
Without any rule in front of it, every call an agent makes to pixi.app.renderStats 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.app.renderStats 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.app.renderStats, this is the rule to start with:
pixi.app.renderStats 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.app.renderStats call is checked against it from then on.
Questions about pixi.app.renderStats
Render-loop counters sampled by hooking the renderer (rolling average over the last frames): draw calls, render time, measured FPS, container/leaf counts. The first call installs the hook — call again after a few frames for populated samples. It is categorised as a Other tool in the Pixi Inspector MCP Server, which means it performs auxiliary operations.
pixi.app.renderStats 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 pixi.app.renderStats: 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.app.renderStats 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.app.renderStats 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.app.renderStats. 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.app.renderStats 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