Medium Risk

browser_set_viewport

Resize the browser viewport in an existing session. Useful for testing responsive layouts without starting a new session — e.g. switch between desktop (1280×800), tablet (820×1180), and mobile (393×852). Returns a screenshot after resizing.

Part of the Screenshotsmcp MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

AI agents use browser_set_viewport to create or modify resources in Screenshotsmcp. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

Without a policy, an AI agent could call browser_set_viewport repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Screenshotsmcp.

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

relievedattention992-smithery-screenshotsmcp.yaml
tools:
  browser_set_viewport:
    rules:
      - action: allow
        rate_limit:
          max: 30
          window: 60

See the full Screenshotsmcp policy for all 56 tools.

Tool Name browser_set_viewport
Category Write
Risk Level Medium

View all 56 tools →

Agents calling write-class tools like browser_set_viewport have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

What does the browser_set_viewport tool do? +

Resize the browser viewport in an existing session. Useful for testing responsive layouts without starting a new session — e.g. switch between desktop (1280×800), tablet (820×1180), and mobile (393×852). Returns a screenshot after resizing.. It is categorised as a Write tool in the Screenshotsmcp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on browser_set_viewport? +

Add a rule in your Intercept YAML policy under the tools section for browser_set_viewport. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Screenshotsmcp MCP server.

What risk level is browser_set_viewport? +

browser_set_viewport is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit browser_set_viewport? +

Yes. Add a rate_limit block to the browser_set_viewport rule in your Intercept 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 browser_set_viewport completely? +

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

browser_set_viewport is provided by the Screenshotsmcp MCP server (relievedattention992-smithery/screenshotsmcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Screenshotsmcp

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

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

Message sent.

We'll get back to you soon.