track_indexeddb

Enable or disable IndexedDB tracking for an origin. Args: origin: Security origin to track enable: Whether to enable or disable tracking Returns: Tracking status

SERVERChrome Devtools SOURCEbenjaminr/chrome-devtools-mcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/benjaminr-chrome-devtools-mcp/track-indexeddb.md

WHAT IT DOES

What track_indexeddb does on Chrome Devtools

AI agents invoke track_indexeddb to trigger actions in Chrome Devtools. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

RISK

Why track_indexeddb is rated High

This tool activates or deactivates IndexedDB tracking in the browser for a given origin. It doesn't just read data or write user content, but rather triggers a browser-level monitoring/instrumentation operation. This is an Execute-category action as it controls browser DevTools behavior. Misuse could enable surveillance of IndexedDB activity for any origin, but it doesn't directly destroy or move data.

From the tool's definition 'Enable or disable IndexedDB tracking for an origin' — triggers an external browser operation (tracking toggle) via Chrome DevTools Protocol

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs track_indexeddb safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Chrome Devtools, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For track_indexeddb, this is the rule to start with:

track_indexeddb Rate-limited

track_indexeddb stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "track_indexeddb": {
      "limits": [
        {
          "counter": "track_indexeddb_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Chrome Devtools, apply this rule, and every track_indexeddb call is checked against it from then on.

FAQ

Questions about track_indexeddb

What does the track_indexeddb tool do? +

Enable or disable IndexedDB tracking for an origin. Args: origin: Security origin to track enable: Whether to enable or disable tracking Returns: Tracking status. It is categorised as a Execute tool in the Chrome Devtools MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on track_indexeddb? +

Register the Chrome Devtools MCP server in PolicyLayer and add a rule for track_indexeddb: 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 Chrome Devtools. Nothing to install.

What risk level is track_indexeddb? +

track_indexeddb is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit track_indexeddb? +

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

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

track_indexeddb is provided by the Chrome Devtools MCP server (benjaminr/chrome-devtools-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Chrome Devtools, and thousands of servers like it.

This server

All 47 Chrome Devtools tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →