sdk_screenshot_after
AI agents call sdk_screenshot_after to retrieve information from UI Bridge MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Screenshot capture is a read-only operation that retrieves visual data from the UI without modifying, executing, or deleting anything. The naming pattern (sdk_screenshot_*) and sibling tools confirm this is observational. While the empty description creates some ambiguity, the most reasonable interpretation is passive screen capture, classifying it as Read with low severity.
From the tool's definition Tool name 'sdk_screenshot_after' and server context indicate screen capture functionality. The 'screenshot' naming convention and placement among sibling tools (diagnose_stuck_screen, get_idle_status, sdk_annotated_screenshot) suggests image retrieval with no…
Attacks that exploit this kind of access
sdk_screenshot_after. It is categorised as a Read tool in the UI Bridge MCP MCP Server, which means it retrieves data without modifying state.
Register the UI Bridge MCP server in PolicyLayer and add a rule for sdk_screenshot_after: 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 UI Bridge MCP. Nothing to install.
sdk_screenshot_after 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 sdk_screenshot_after 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 sdk_screenshot_after. 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.
sdk_screenshot_after is provided by the UI Bridge MCP server (qontinui/ui-bridge-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →