chrome · MCP Lite Wrappers MCP: Risk & Policy

WHAT IT DOES

What chrome does on MCP Lite Wrappers

AI agents invoke chrome to trigger actions in MCP Lite Wrappers. 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.

WHY IT NEEDS A POLICY

Why chrome needs a policy

Given the server context mentions Chrome DevTools integration, this tool likely controls a Chrome browser instance, enabling browser automation such as navigation, clicking, script execution, and DOM manipulation — all Execute-category actions with high blast radius. Confidence is moderate due to the empty description.

From the tool's definition Tool name is 'chrome' on a server that wraps Chrome DevTools; description is empty and uninformative.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

chrome Rate-limited

chrome 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": {
    "chrome": {
      "limits": [
        {
          "counter": "chrome_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches MCP Lite Wrappers, so you can run agents against it safely.

FAQ

Questions about chrome

What does the chrome tool do? +

chrome. It is categorised as a Execute tool in the MCP Lite Wrappers MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on chrome? +

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

What risk level is chrome? +

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

Can I rate-limit chrome? +

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

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

chrome is provided by the MCP Lite Wrappers MCP server (sbraind/mcp-lite-wrappers). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

chrome is one line of MCP Lite Wrappers's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

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