// SCAN REPORT

Chrome MCP Server (Security Hardened)

7 tools. 4 can modify or destroy data without limits.

1 destructive tool with no built-in limits. Policy required.

Last updated: 12 Jun 2026

4 can modify or destroy data

3 read-only

7 tools total

Community server · catalogue entry verified 12/06/2026

How to control Chrome MCP Server (Security Hardened) ↓

TOOL MAP

What Chrome MCP Server (Security Hardened) exposes to your agents

Read (3) Write / Execute (3) Destructive / Financial (1)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous Chrome MCP Server (Security Hardened) tools

Destructive · High delete_credential This tool irreversibly deletes data (stored credentials) and cannot be undone, which is the defining characteristic of the Destructive category. Execute · High secure_login This tool performs browser automation actions: locating form fields, injecting stored credentials, and submitting a login form. Write · High update_credential This tool modifies existing credential data reversibly. Write · High store_credential This tool writes sensitive credential data (usernames, passwords) into an encrypted vault.

4 of Chrome MCP Server (Security Hardened)'s 7 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Chrome MCP Server (Security Hardened)

PolicyLayer is an MCP gateway — it sits between your AI agents and Chrome MCP Server (Security Hardened), and nothing reaches the server without passing your rules. These are the rules we recommend:

Deny destructive operations

{
  "delete_credential": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations

{
  "store_credential": {
    "limits": [
      {
        "counter": "store_credential_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "get_credential": {
    "limits": [
      {
        "counter": "get_credential_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Chrome MCP Server (Security Hardened) — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON CHROME MCP SERVER (SECURITY HARDENED) →

Free to start. No card required.

FULL CATALOGUE

All 7 Chrome MCP Server (Security Hardened) tools

DESTRUCTIVE 1 tools

Destructive delete_credential Permanently delete a stored credential.

EXECUTE 1 tools

Execute secure_login Perform a secure login using stored credentials. Automatically fills in username/email and password fields, th

WRITE 2 tools

Write store_credential Securely store login credentials with post-quantum encryption. Credentials are encrypted at rest and wiped fro Write update_credential Update an existing credential. Only provided fields will be updated.

READ 3 tools

Read get_credential Get a specific credential by ID. Returns metadata only - use secure_login for authentication. Read get_vault_status Get the status of the credential vault including encryption configuration. Read list_credentials List all stored credentials. Returns metadata only - no passwords or API keys are exposed.

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about Chrome MCP Server (Security Hardened)

Can an AI agent delete data through the Chrome MCP Server (Security Hardened) MCP server? +

Yes. The Chrome MCP Server (Security Hardened) server exposes 1 destructive tools including delete_credential. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through Chrome MCP Server (Security Hardened)? +

The Chrome MCP Server (Security Hardened) server has 2 write tools including store_credential, update_credential. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Chrome MCP Server (Security Hardened).

How many tools does the Chrome MCP Server (Security Hardened) MCP server expose? +

7 tools across 3 categories: Destructive, Read, Write. 3 are read-only. 4 can modify, create, or delete data.

How do I enforce a policy on Chrome MCP Server (Security Hardened)? +

Register the Chrome MCP Server (Security Hardened) MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Chrome MCP Server (Security Hardened) tool call.

Deterministic rules across all 7 Chrome MCP Server (Security Hardened) tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON CHROME MCP SERVER (SECURITY HARDENED) →

Free to start. No card required.

7 Chrome MCP Server (Security Hardened) tools catalogued and risk-classified — across an index of 43,000+ MCP servers.