reflect_get_screenshot
Capture a screenshot from the current state of an active Reflect recording session Parameters: - sessionId (string) *required*: The ID of the Reflect recording session - format (enum): The image format for the screenshot (png or jpeg)
This record as markdown: /tools/smartbear-mcp/reflect-get-screenshot.md
What reflect_get_screenshot does on SmartBear MCP
AI agents call reflect_get_screenshot to retrieve information from SmartBear MCP 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 |
|---|---|---|---|
format | string | — | The image format for the screenshot (png or jpeg) |
sessionId | string | Yes | The ID of the Reflect recording session |
Parameters from the server's own tool schema.
Why reflect_get_screenshot is rated Low
This tool retrieves a screenshot from an active recording session without modifying, deleting, or executing operations. It is a read-only operation that queries the current state of a Reflect session. The parameters (sessionId and format) are for specifying what to retrieve, not for making changes.
From the tool's definition Tool name 'reflect_get_screenshot' and description state it 'Capture a screenshot from the current state of an active Reflect recording session'.
Attacks that exploit this kind of access
The rule that runs reflect_get_screenshot safely
PolicyLayer is an MCP gateway: it sits between your AI agents and SmartBear MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For reflect_get_screenshot, this is the rule to start with:
reflect_get_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 SmartBear MCP, apply this rule, and every reflect_get_screenshot call is checked against it from then on.
Questions about reflect_get_screenshot
Capture a screenshot from the current state of an active Reflect recording session Parameters: - sessionId (string) *required*: The ID of the Reflect recording session - format (enum): The image format for the screenshot (png or jpeg). It is categorised as a Read tool in the SmartBear MCP MCP Server, which means it retrieves data without modifying state.
reflect_get_screenshot accepts 2 parameters: format, sessionId. Required: sessionId. The full parameter table on this page comes from the server's own tool schema.
Register the SmartBear MCP server in PolicyLayer and add a rule for reflect_get_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 SmartBear MCP. Nothing to install.
reflect_get_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 reflect_get_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 reflect_get_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.
reflect_get_screenshot is provided by the SmartBear MCP server (SmartBear/smartbear-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on SmartBear, and thousands of servers like it.
This server
Across the catalogue