session.auth

THE RISK

High Risk

Why session.auth needs a policy

This tool executes a sequence of actions to perform authentication, which involves browser automation steps (clicks, form fills, navigation). It triggers external operations whose effects depend on arguments — namely logging into systems, which could be misused to authenticate as arbitrary users or services.

From the tool's definition Perform authentication by executing a sequence of actions

Documented attack patterns abuse exactly the kind of access session.auth gives an agent:

POLICY

How to control session.auth

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

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "session.auth": {
      "limits": [
        {
          "counter": "session.auth_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

session.auth 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 LCBro — 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 LCBro tools

Execute interact.click Click on an element using CSS selector, text, or role Execute interact.wait Wait for a condition (selector, network idle, or URL change) Execute llm.transform Transform data using LLM with custom instructions and JSON schema validation Execute navigate.goto Navigate to a URL in an existing page context Execute navigate.open Open a URL and create a new page context Write interact.type Type text into an input field Read extract.attributes Extract attributes from elements matching CSS selectors Read extract.content Extract page content in various formats (text, html, markdown, readability)

All 11 LCBro 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 LCBro → 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 session.auth

What does the session.auth tool do? +

Perform authentication by executing a sequence of actions. It is categorised as a Execute tool in the LCBro MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on session.auth? +

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

What risk level is session.auth? +

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

Can I rate-limit session.auth? +

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

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

session.auth is provided by the LCBro MCP server (lcbro/lcbro-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every LCBro tool call.

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

CHECK YOUR STACK →