ext.storage.get
OWNER-ONLY. Reads chrome.storage (bounded; sensitive values such as the pairing token are REDACTED to a length placeholder). 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.storage.get.md
What ext.storage.get does on Pixi Inspector
AI agents call ext.storage.get to retrieve information from Pixi Inspector without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
area | string | — | chrome.storage area (default local). |
keys | object | — | Key or keys to read (omit = all keys in the area). |
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.storage.get is rated Low
Even though ext.storage.get only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs ext.storage.get 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.storage.get, this is the rule to start with:
ext.storage.get is read-only, so it stays allowed. 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 ext.storage.get call is checked against it from then on.
Questions about ext.storage.get
OWNER-ONLY. Reads chrome.storage (bounded; sensitive values such as the pairing token are REDACTED to a length placeholder). 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 Read tool in the Pixi Inspector MCP Server, which means it retrieves data without modifying state.
ext.storage.get accepts 3 parameters: area, keys, 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.storage.get: 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.storage.get is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the ext.storage.get 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.storage.get. 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.storage.get 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