web_show

Brings a web session's browser window to the FRONT so the USER can take over directly — solve a CAPTCHA, complete 2FA, or make a choice the AI shouldn't. Local MCP never solves CAPTCHAs itself; this hands control to the user. Pair with web_screenshot first to show them what's on the page. After t...

SERVERLocal SOURCElocal-mcp
High RISK CLASS
Category Execute
Parameters 20 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-local-mcp-local-mcp/web-show.md

What web_show does on Local

AI agents invoke web_show 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.

ParameterTypeRequiredDescription
reason string Short reason shown to the user, e.g. 'a CAPTCHA appeared' or 'confirm which account'.
session string Session name (default 'default').

Parameters from the server's own tool schema.

Why web_show is rated High

This tool triggers an external browser window action — bringing a window to the foreground — which is an operation that affects the user's environment. It doesn't read, write, or delete data, but it executes a UI/system action (window focus manipulation).

From the tool's definition Brings a web session's browser window to the FRONT

Questions about web_show

What does the web_show tool do? +

Brings a web session's browser window to the FRONT so the USER can take over directly — solve a CAPTCHA, complete 2FA, or make a choice the AI shouldn't. Local MCP never solves CAPTCHAs itself; this hands control to the user. Pair with web_screenshot first to show them what's on the page. After they finish, tell the agent to continue — the session keeps its state. 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.

What parameters does web_show accept? +

web_show accepts 2 parameters: reason, session. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on web_show? +

Register the Local MCP server in PolicyLayer and add a rule for web_show: 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.

What risk level is web_show? +

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

Can I rate-limit web_show? +

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

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

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

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Local's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.