Capture a real pixel screenshot of the user's tab. Unlike the DOM/style tools, this returns what the browser actually painted — true fonts, cross-origin images, shadows, gradients, blend modes. Use it for design review and visual-fidelity checks the DOM can't answer. Requires the user to have tic...
Risk signalsHandles credentials or secrets (secret)
Part of the Sncro server.
Free to start. No card required.
AI agents call get_screenshot to retrieve information from Sncro without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though get_screenshot only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"get_screenshot": {}
}
}See the full Sncro policy for all 12 tools.
These attack patterns abuse exactly the kind of access get_screenshot gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
Capture a real pixel screenshot of the user's tab. Unlike the DOM/style tools, this returns what the browser actually painted — true fonts, cross-origin images, shadows, gradients, blend modes. Use it for design review and visual-fidelity checks the DOM can't answer. Requires the user to have ticked "Allow screenshots" on the consent screen AND to have clicked "Share" on the sncro badge to start the screen-share (a one-time per-session browser prompt). If you get SCREENSHOTS_NOT_CONSENTED, ask the user to create a new session with that box checked. If you get SCREENSHOTS_NOT_STARTED, ask them to click "Share" on the sncro badge in the page corner. Args: key: The sncro session key secret: The session secret from create_session max_width: Max image width in px; the frame is scaled down to fit (default 1280). It is categorised as a Read tool in the Sncro MCP Server, which means it retrieves data without modifying state.
Register the Sncro MCP server in PolicyLayer and add a rule for 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 Sncro. Nothing to install.
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 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 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.
get_screenshot is provided by the Sncro MCP server (https://relay.sncro.net/tools/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 12 Sncro tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.