ext.storage.remove

SERVERPixi Inspector SOURCEpixi-inspector-mcp

Low RISK CLASS

Category Other

Parameters 31 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/pixi-inspector-mcp/ext.storage.remove.md

WHAT IT DOES

What ext.storage.remove does on Pixi Inspector

AI agents call ext.storage.remove as a supporting operation in Pixi Inspector workflows.

Parameter	Type	Required	Description
`area`	string	—	chrome.storage area (default local).
`keys`	object	Yes	Key or keys to remove.
`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.

RISK

Why ext.storage.remove is rated Low

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

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs ext.storage.remove 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.remove, this is the rule to start with:

ext.storage.remove Rate-limited

ext.storage.remove gets a rate cap, and everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "ext.storage.remove": {
      "limits": [
        {
          "counter": "ext.storage.remove_rate",
          "window": "minute",
          "max": 60,
          "scope": "grant"
        }
      ]
    }
  }
}

SET A RULE FOR THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Pixi Inspector, apply this rule, and every ext.storage.remove call is checked against it from then on.

FAQ

Questions about ext.storage.remove

What does the ext.storage.remove tool do? +

OWNER-ONLY, DESTRUCTIVE. Removes keys from chrome.storage. In the local area, keys of the mcp* / pixiMcp* families (the extension's own control state: tab allowlist, connector switch, pairing token, instance id and label) are refused with BAD_PARAMS listing them in data.refused, and nothing from that call is removed. 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 Other tool in the Pixi Inspector MCP Server, which means it performs auxiliary operations.

What parameters does ext.storage.remove accept? +

ext.storage.remove accepts 3 parameters: area, keys, target. Required: keys. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on ext.storage.remove? +

Register the Pixi Inspector MCP server in PolicyLayer and add a rule for ext.storage.remove: 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 ext.storage.remove? +

ext.storage.remove is a Other tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit ext.storage.remove? +

Yes. Add a rate_limit block to the ext.storage.remove 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 ext.storage.remove completely? +

Set action: deny in the PolicyLayer policy for ext.storage.remove. 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 ext.storage.remove? +

ext.storage.remove 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.

KEEP EXPLORING

More on Pixi Inspector, and thousands of servers like it.

This server

All 63 Pixi Inspector tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Tool risk categories →MCP tool →