ext.logs
OWNER-ONLY. Returns recent service-worker console output from a bounded in-memory ring buffer (drop-oldest). UNAUTHORIZED unless that browser is paired. Runs in one browser: target picks it (does not pin), else the chosen tab's browser.
This record as markdown: /tools/pixi-inspector-mcp/ext.logs.md
What ext.logs does on Pixi Inspector
AI agents call ext.logs 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 |
|---|---|---|---|
level | string | — | Filter by level. |
limit | integer | — | Max entries (most recent; cap 1000, default 100). |
target | string | — | Run in a specific browser: any target id of it, like "b7a3c1#487", from status/use_target/CHOOSE_TARGET (only the browser part is used). Omit to use the browser |
Parameters from the server's own tool schema.
Why ext.logs is rated Critical
An AI agent that decides to call ext.logs 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 ext.logs 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 ext.logs, this is the rule to start with:
ext.logs 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 ext.logs call is checked against it from then on.
Questions about ext.logs
OWNER-ONLY. Returns recent service-worker console output from a bounded in-memory ring buffer (drop-oldest). UNAUTHORIZED unless that browser is paired. Runs in one browser: target picks it (does not pin), else the chosen tab's browser. 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.
ext.logs accepts 3 parameters: level, limit, target. 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 ext.logs: 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.
ext.logs 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 ext.logs 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 ext.logs. 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.
ext.logs 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