browser_resize
Resize the page viewport. Useful when a site serves different HTML based on viewport width (mobile vs desktop) or when an anti-bot scores risk by viewport dimensions.
This record as markdown: /tools/io-github-saloprj-dialogbrain/browser-resize.md
What browser_resize does on Dialogbrain
AI agents invoke browser_resize to trigger actions in Dialogbrain. 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 |
|---|---|---|---|
width | integer | Yes | |
height | integer | Yes | |
page_id | string | Yes |
Parameters from the server's own tool schema.
Why browser_resize is rated High
This tool executes a browser-level action (resizing the viewport), which is an external operation affecting browser state. It's not purely a read operation, and the mention of bypassing anti-bot scoring raises additional concern about potential misuse for evasion purposes. It fits Execute as it triggers browser actions whose effects depend on arguments.
From the tool's definition 'Resize the page viewport' and 'when an anti-bot scores risk by viewport dimensions' — triggers a browser action that modifies the viewport state and can be used to manipulate anti-bot detection
Attacks that exploit this kind of access
The rule that runs browser_resize safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Dialogbrain, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For browser_resize, this is the rule to start with:
browser_resize 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 Dialogbrain, apply this rule, and every browser_resize call is checked against it from then on.
Questions about browser_resize
Resize the page viewport. Useful when a site serves different HTML based on viewport width (mobile vs desktop) or when an anti-bot scores risk by viewport dimensions. It is categorised as a Execute tool in the Dialogbrain MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
browser_resize accepts 3 parameters: width, height, page_id. Required: width, height, page_id. The full parameter table on this page comes from the server's own tool schema.
Register the Dialogbrain MCP server in PolicyLayer and add a rule for browser_resize: 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 Dialogbrain. Nothing to install.
browser_resize 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 browser_resize 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 browser_resize. 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.
browser_resize is provided by the Dialogbrain MCP server (https://api.dialogbrain.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Dialogbrain, and thousands of servers like it.
Across the catalogue