selenium_screenshot
Capture a PNG screenshot from a Selenium session. Returns base64 PNG.
This record as markdown: /tools/io-github-kivanccakmak-yaver/selenium-screenshot.md
What selenium_screenshot does on Yaver
AI agents call selenium_screenshot to retrieve information from Yaver without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
session_id | string | Yes | Selenium session ID |
Parameters from the server's own tool schema.
Why selenium_screenshot is rated Low
This tool only captures and returns a screenshot (read-only observation of browser state). It does not modify, execute, or delete anything; it purely retrieves visual state as a base64 PNG image.
From the tool's definition Capture a PNG screenshot from a Selenium session. Returns base64 PNG.
Attacks that exploit this kind of access
The rule that runs selenium_screenshot safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Yaver, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For selenium_screenshot, this is the rule to start with:
selenium_screenshot is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Yaver, apply this rule, and every selenium_screenshot call is checked against it from then on.
Questions about selenium_screenshot
Capture a PNG screenshot from a Selenium session. Returns base64 PNG. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.
selenium_screenshot accepts 1 parameter: session_id. Required: session_id. The full parameter table on this page comes from the server's own tool schema.
Register the Yaver MCP server in PolicyLayer and add a rule for selenium_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 Yaver. Nothing to install.
selenium_screenshot is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the selenium_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.
Set action: deny in the PolicyLayer policy for selenium_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.
selenium_screenshot is provided by the Yaver MCP server (yaver-cli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Yaver, and thousands of servers like it.
This server
Across the catalogue