New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

pixi.app.stats

Engine diagnostics: engine (PIXI|PHASER), pixiVersion, rendererType (webgl/webgpu/canvas), resolution, screen size, FPS, frame time, average draw calls per frame, and node count. Phaser fills only what it exposes.

SERVERPixi Inspector SOURCEpixi-inspector-mcp
Low RISK CLASS
Category Other
Parameters 30 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/pixi-inspector-mcp/pixi.app.stats.md

What pixi.app.stats does on Pixi Inspector

AI agents call pixi.app.stats as a supporting operation in Pixi Inspector workflows.

ParameterTypeRequiredDescription
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.stats is rated Low

Without any rule in front of it, every call an agent makes to pixi.app.stats happens silently: no trail, no cap, no way to know it misbehaved until something breaks downstream.

Questions about pixi.app.stats

What does the pixi.app.stats tool do? +

Engine diagnostics: engine (PIXI|PHASER), pixiVersion, rendererType (webgl/webgpu/canvas), resolution, screen size, FPS, frame time, average draw calls per frame, and node count. Phaser fills only what it exposes. It is categorised as a Other tool in the Pixi Inspector MCP Server, which means it performs auxiliary operations.

What parameters does pixi.app.stats accept? +

pixi.app.stats accepts 3 parameters: tabId, target, frameId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on pixi.app.stats? +

Register the Pixi Inspector MCP server in PolicyLayer and add a rule for pixi.app.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.

What risk level is pixi.app.stats? +

pixi.app.stats is a Other tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit pixi.app.stats? +

Yes. Add a rate_limit block to the pixi.app.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.

How do I block pixi.app.stats completely? +

Set action: deny in the PolicyLayer policy for pixi.app.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.

What MCP server provides pixi.app.stats? +

pixi.app.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

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Pixi Inspector's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.