session_start

A execute tool on the Looking Glass MCP server.

SERVERLooking Glass SOURCElooking-glass-mcp

High RISK CLASS

Category Execute

Parameters 10 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-sahib-sawhney-wh-looking-glass-mcp/session-start.md

WHAT IT DOES

What session_start does on Looking Glass

AI agents invoke session_start to trigger actions in Looking Glass. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

Parameter	Type	Required	Description
`name`	string	—	Optional session name

Parameters from the server's own tool schema.

RISK

Why session_start is rated High

Despite the empty description, the tool's name 'session_start' on a browser automation MCP server indicates it initiates browser sessions—a capability that can trigger external operations and side effects depending on how sessions are configured. This falls under Execute rather than Write because browser sessions enable arbitrary browsing actions whose effects depend on subsequent agent behavior.

From the tool's definition Tool named 'session_start' on an 'AI-native browser for agents' server with 72 tools including browser automation capabilities like 'browser_click', 'browser_close', 'browser_analyze_page'.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs session_start safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Looking Glass, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For session_start, this is the rule to start with:

session_start Rate-limited

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

View as policy code

policy.json

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

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Looking Glass, apply this rule, and every session_start call is checked against it from then on.

FAQ

Questions about session_start

What does the session_start tool do? +

session_start is a execute tool on the Looking Glass MCP server. It is categorised as a Execute tool in the Looking Glass MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

What parameters does session_start accept? +

session_start accepts 1 parameter: name. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on session_start? +

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

What risk level is session_start? +

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

Can I rate-limit session_start? +

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

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

session_start is provided by the Looking Glass MCP server (looking-glass-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Looking Glass, and thousands of servers like it.

This server

All 71 Looking Glass tools → High-risk tools on this server →

Across the catalogue

start_devtools_monitoring on Percepta MCP Server →team_manager_start_room on Team Manager MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →