browser_screenshot

A execute tool on the MCP Framework Personal MCP server.

SERVERMCP Framework Personal SOURCEinggerman/mcps

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/inggerman-mcps/browser-screenshot.md

WHAT IT DOES

What browser_screenshot does on MCP Framework Personal

AI agents invoke browser_screenshot to trigger actions in MCP Framework Personal. 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.

RISK

Why browser_screenshot is rated High

Browser screenshot tools typically execute browser actions to capture the current state of a browser session. This falls under Execute as it involves triggering external browser operations. The severity is high because browser automation tools can expose sensitive on-screen information and may imply broader browser control capabilities. Confidence is reduced due to the empty description.

From the tool's definition Tool name 'browser_screenshot' implies browser automation/interaction. Description is empty and uninformative.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs browser_screenshot safely

PolicyLayer is an MCP gateway: it sits between your AI agents and MCP Framework Personal, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For browser_screenshot, this is the rule to start with:

browser_screenshot Rate-limited

browser_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_screenshot": {
      "limits": [
        {
          "counter": "browser_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 MCP Framework Personal, apply this rule, and every browser_screenshot call is checked against it from then on.

FAQ

Questions about browser_screenshot

What does the browser_screenshot tool do? +

browser_screenshot is a execute tool on the MCP Framework Personal MCP server. It is categorised as a Execute tool in the MCP Framework Personal MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on browser_screenshot? +

Register the MCP Framework Personal MCP server in PolicyLayer and add a rule for browser_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 MCP Framework Personal. Nothing to install.

What risk level is browser_screenshot? +

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

Can I rate-limit browser_screenshot? +

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

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

browser_screenshot is provided by the MCP Framework Personal MCP server (inggerman/mcps). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on MCP Framework Personal, and thousands of servers like it.

This server

All 811 MCP Framework Personal 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 →