login_classic

THE RISK

High Risk

Why login_classic needs a policy

This tool automates login flows on third-party authentication systems (Google, Microsoft, generic SSO). It executes browser actions (typing credentials, submitting forms) that establish authenticated sessions. Misuse could lead to unauthorized account access or credential harvesting. It falls under Execute as it orchestrates external browser operations whose effects depend on the credentials and target site provided.

From the tool's definition 'Composite login for classic email→password forms (Google, Microsoft, generic SSO)' — triggers a multi-step browser automation sequence involving form filling and submission on authentication systems

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

POLICY

How to control login_classic

PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Camoufox, and nothing reaches the server without passing your rules. This is the rule we recommend for login_classic:

policy.json

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

login_classic 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 MCP Camoufox — 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 MCP Camoufox tools

Destructive cookie_delete Delete cookies. Both empty = clear all. Destructive localstorage_clear Clear all localStorage. Destructive reset_profile Delete the persistent profile (~/.camoufox-mcp/profile) entirely. Destructive browser_close Close the browser. Cookies are preserved in the persistent profile (~/.camoufox-mcp/profil Destructive tab_close Close a tab by index (-1 = active), or by url_contains. Execute batch_actions Execute multiple actions in one call. Each action: {type, ref?, value?, text?, key?, url?} Execute browser_launch Launch Camoufox stealth browser and navigate to URL. Browser persists between calls. Execute evaluate Execute JavaScript in page context.

All 102 MCP Camoufox 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 MCP Camoufox → 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 login_classic

What does the login_classic tool do? +

Composite login for classic email→password forms (Google, Microsoft, generic SSO). It is categorised as a Execute tool in the MCP Camoufox MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on login_classic? +

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

What risk level is login_classic? +

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

Can I rate-limit login_classic? +

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

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

login_classic is provided by the MCP Camoufox MCP server (robithyusuf/mcp-camoufox). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every MCP Camoufox tool call.

Start from MCP Camoufox, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →