browser_take_screenshot

SERVERDialogbrain SOURCEhttps://api.dialogbrain.com/mcp

High RISK CLASS

Category Execute

Parameters 41 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-saloprj-dialogbrain/browser-take-screenshot.md

WHAT IT DOES

What browser_take_screenshot does on Dialogbrain

AI agents invoke browser_take_screenshot 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
`ref`	object	—
`page_id`	string	Yes
`full_page`	boolean	—
`inline_bytes`	boolean	—

Parameters from the server's own tool schema.

RISK

Why browser_take_screenshot is rated High

This tool triggers a browser action (capturing a screenshot) and persists the result to external storage, producing side effects beyond simple data retrieval. It executes a browser operation and writes a file to DialogBrain's storage system. The blast radius is medium — it could capture sensitive on-screen content and store/transmit it, but it doesn't directly delete data or move money.

From the tool's definition Capture a PNG screenshot of the page or a specific element. Returns base64-encoded image bytes AND a file_id (persisted in DialogBrain files storage).

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs browser_take_screenshot 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_take_screenshot, this is the rule to start with:

browser_take_screenshot Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "browser_take_screenshot": {
      "limits": [
        {
          "counter": "browser_take_screenshot_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Dialogbrain, apply this rule, and every browser_take_screenshot call is checked against it from then on.

FAQ

Questions about browser_take_screenshot

What does the browser_take_screenshot tool do? +

Capture a PNG screenshot of the page or a specific element. Returns base64-encoded image bytes AND a file_id (persisted in DialogBrain files storage). Pass file_id straight to messages.send(attachment_file_ids=[file_id]) — do NOT call files.upload again. Use sparingly — favor browser.snapshot for structured DOM understanding. 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.

What parameters does browser_take_screenshot accept? +

browser_take_screenshot accepts 4 parameters: ref, page_id, full_page, inline_bytes. Required: page_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on browser_take_screenshot? +

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

What risk level is browser_take_screenshot? +

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

Can I rate-limit browser_take_screenshot? +

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

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

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

KEEP EXPLORING

More on Dialogbrain, and thousands of servers like it.

This server

All 225 Dialogbrain tools → High-risk tools on this server →

Across the catalogue

browser_click on Percepta MCP Server → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →