sdk_screenshot_baseline_save
AI agents use sdk_screenshot_baseline_save to create or update resources in UI Bridge MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your UI Bridge MCP environment.
The tool name implies it captures and persists a screenshot as a baseline reference, which is a write operation (creating/overwriting a stored artifact). The description is empty, lowering confidence. Severity is medium because overwriting a baseline could corrupt UI testing workflows, but it is reversible by saving a new baseline.
From the tool's definition Tool name: sdk_screenshot_baseline_save — the word 'save' implies writing/storing data; 'baseline' suggests it stores a reference screenshot for future comparisons.
Attacks that exploit this kind of access
sdk_screenshot_baseline_save. It is categorised as a Write tool in the UI Bridge MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the UI Bridge MCP server in PolicyLayer and add a rule for sdk_screenshot_baseline_save: 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_baseline_save is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the sdk_screenshot_baseline_save 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_baseline_save. 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_baseline_save 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 →