login

Q: What risk level is login?

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

THE RISK

High Risk

Why login needs a policy

This tool launches a browser (Chromium) and performs browser automation to establish an authenticated session. It executes an external process (browser) and triggers an interactive login flow. It does not directly read, write, or delete data, but it does execute browser automation that has side effects (session creation), placing it in the Execute category.

From the tool's definition Opens a visible Chromium browser to log in to Frisco manually. Run this first to establish a session.

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

POLICY

How to control login

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

policy.json

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

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 Frisco MCP — 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 Frisco MCP tools

Financial finish_session Opens the browser at the checkout page so you can select a delivery time and pay. Destructive clear_cart Empties the Frisco cart using the site Destructive clear_session Clears the saved session and closes the browser. Destructive remove_item_from_cart Removes a specific product from the Frisco cart by name (partial match supported). Write add_items_to_cart Adds products to cart by selecting from the most recent search_products result page. No ad Write update_item_quantity Changes the quantity of a product already in the cart (partial name match supported). Read check_cart_issues Checks the cart for sold-out or unavailable products and lists available substitutes for e Read get_logs Returns persisted JSONL log events for the current or selected session.

All 15 Frisco MCP 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 Frisco MCP → 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

What does the login tool do? +

Opens a visible Chromium browser to log in to Frisco manually. Run this first to establish a session. It is categorised as a Execute tool in the Frisco MCP 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? +

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

What risk level is login? +

Can I rate-limit login? +

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

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

login is provided by the Frisco MCP server (mkidawa/frisco-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Frisco MCP tool call.

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

CHECK YOUR STACK →