secure_login

THE RISK

High Risk

Why secure_login needs a policy

This tool performs browser automation actions: locating form fields, injecting stored credentials, and submitting a login form. It triggers external operations (authentication to third-party services) whose effects depend on which credentials and target site are used.

From the tool's definition Automatically fills in username/email and password fields, then submits the form

Documented attack patterns abuse exactly the kind of access secure_login gives an agent:

POLICY

How to control secure_login

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. This is the rule we recommend for secure_login:

policy.json

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

secure_login 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.

Create a free account and register Chrome MCP Server (Security Hardened) — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RATE-LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Chrome MCP Server (Security Hardened) tools

Destructive delete_credential Permanently delete a stored credential. Write store_credential Securely store login credentials with post-quantum encryption. Credentials are encrypted a Write update_credential Update an existing credential. Only provided fields will be updated. Read get_credential Get a specific credential by ID. Returns metadata only - use secure_login for authenticati 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.

All 7 Chrome MCP Server (Security Hardened) tools →

Execute tools on other servers

Android Forensics ADB MCP Server adb_shell_command EMBA-MCP run_emba_scan Frida Game Hacking MCP remove_breakpoint Procmon request_elevation

Go deeper

High-risk tools in Chrome MCP Server (Security Hardened) → Every high-risk tool this server exposes, in one view.
All high-risk MCP tools → Every high-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Agent sandbox → Bounding what an agent can execute and where the boundary should sit.
Least privilege for MCP → Granting agents the minimum tool surface the task needs.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about secure_login

What does the secure_login tool do? +

Perform a secure login using stored credentials. Automatically fills in username/email and password fields, then submits the form. It is categorised as a Execute tool in the Chrome MCP Server (Security Hardened) MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on secure_login? +

Register the Chrome MCP Server (Security Hardened) MCP server in PolicyLayer and add a rule for secure_login: 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 MCP Server (Security Hardened). Nothing to install.

What risk level is secure_login? +

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

Can I rate-limit secure_login? +

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

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

secure_login is provided by the Chrome MCP Server (Security Hardened) MCP server (pantheon-security/chrome-mcp-secure). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

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

Start from Chrome MCP Server (Security Hardened), add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →