AI agents call screen.get_frame to retrieve information from Third Eye without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves/queries recorded frame data without side effects. However, severity is high because screen recordings may contain sensitive information (passwords, private communications, financial data, PII), and an AI agent could systematically extract and exfiltrate all frames from a recording.
From the tool's definition Tool name is 'screen.get_frame' and description states 'Retrieve a full-resolution frame from a recording' — the verb 'Retrieve' and action of fetching data from an existing recording indicate a read operation with no modification or deletion.
Attacks that exploit this kind of access
Retrieve a full-resolution frame from a recording. Use recordingId from screen.record response. Specify either frameIndex or timestamp. It is categorised as a Read tool in the Third Eye MCP Server, which means it retrieves data without modifying state.
Register the Third Eye MCP server in PolicyLayer and add a rule for screen.get_frame: 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 Third Eye. Nothing to install.
screen.get_frame 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 screen.get_frame 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 screen.get_frame. 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.
screen.get_frame is provided by the Third Eye MCP server (osseni94/third-eye-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
screen.get_frame is one line of Third Eye's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →