web_session_close
Closes a web-automation session's window and frees it. The saved login stays on disk, so web_login/web_navigate can reopen it later without signing in again.
This record as markdown: /tools/com-local-mcp-local-mcp/web-session-close.md
What web_session_close does on Local
AI agents invoke web_session_close to trigger actions in Local. 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 |
|---|---|---|---|
session | string | — | Session name (a named login profile, e.g. 'linkedin'). Defaults to 'default'. |
Parameters from the server's own tool schema.
Why web_session_close is rated High
The tool closes a running browser automation session window, which is an external operation with side effects (terminating a process/window). It is not purely destructive since the saved login persists and the session can be reopened.
From the tool's definition 'Closes a web-automation session's window and frees it' — terminates an active browser session/window
Attacks that exploit this kind of access
The rule that runs web_session_close safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Local, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For web_session_close, this is the rule to start with:
web_session_close 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Local, apply this rule, and every web_session_close call is checked against it from then on.
Questions about web_session_close
Closes a web-automation session's window and frees it. The saved login stays on disk, so web_login/web_navigate can reopen it later without signing in again. It is categorised as a Execute tool in the Local MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
web_session_close accepts 1 parameter: session. The full parameter table on this page comes from the server's own tool schema.
Register the Local MCP server in PolicyLayer and add a rule for web_session_close: 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 Local. Nothing to install.
web_session_close is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the web_session_close 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.
Set action: deny in the PolicyLayer policy for web_session_close. 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.
web_session_close is provided by the Local MCP server (local-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Local, and thousands of servers like it.
Across the catalogue