Connect to web page. If URL provided, opens new tab; otherwise connects to current tab.
AI agents invoke web_connect to trigger actions in Web Bridge. 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 |
|---|---|---|---|
web.url | string | — | URL to open in new tab (omit to use current page) |
web.aiActContext | string | — | Background knowledge passed to aiAct. Default: no extra context. |
web.waitAfterAction | number | — | Wait time in milliseconds after each action execution. Default: 300ms. |
web.replanningCycleLimit | integer | — | Maximum number of replanning cycles for aiAct. Default: model adapter default. |
web.screenshotShrinkFactor | number | — | Screenshot shrink factor before sending images to AI. Default: 1; high values may reduce recognition quality, especially on mobile. |
Parameters from the server's own tool schema.
This tool triggers an external browser operation — opening a new tab or connecting to an existing one. It doesn't just read data; it actively interacts with the browser environment, which can have side effects depending on the URL or page loaded. Given the sibling tools (act, click, input, etc.), this is part of a web automation suite where connecting to a page is a prerequisite for further automated actions.
From the tool's definition Connect to web page. If URL provided, opens new tab; otherwise connects to current tab.
Risk signalsAccepts URL/endpoint input (web.url)
Attacks that exploit this kind of access
Connect to web page. If URL provided, opens new tab; otherwise connects to current tab. It is categorised as a Execute tool in the Web Bridge MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
web_connect accepts 5 parameters: web.url, web.aiActContext, web.waitAfterAction, web.replanningCycleLimit, web.screenshotShrinkFactor. The full parameter table on this page comes from the server's own tool schema.
Register the Web Bridge MCP server in PolicyLayer and add a rule for web_connect: 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 Web Bridge. Nothing to install.
web_connect 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_connect 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_connect. 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_connect is provided by the Web Bridge MCP server (@midscene/web-bridge-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →