Return frames for a screenlog session. Default: metadata only (idx, capturedAt, display, file, active app/window) — cheap, agent-readable, answers 'what was on screen at <time>'. With sample=N, also attach N evenly-spaced frames as INLINE IMAGES so a vision-capable runner can see representative m...
AI agents call screenlog_frames to retrieve information from Yaver without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
id | string | Yes | |
limit | integer | — | return only the last N frames' metadata |
sample | integer | — | attach N evenly-spaced frames as inline images for vision analysis |
Parameters from the server's own tool schema.
Even though screenlog_frames only reads data, uncontrolled read access leaks sensitive information and racks up API costs — an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
Return frames for a screenlog session. Default: metadata only (idx, capturedAt, display, file, active app/window) — cheap, agent-readable, answers 'what was on screen at <time>'. With sample=N, also attach N evenly-spaced frames as INLINE IMAGES so a vision-capable runner can see representative moments. Full images live at /screenlog/<id>/<file>. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.
screenlog_frames accepts 3 parameters: id, limit, sample. Required: id. The full parameter table on this page comes from the server's own tool schema.
Register the Yaver MCP server in PolicyLayer and add a rule for screenlog_frames: 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 Yaver. Nothing to install.
screenlog_frames 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 screenlog_frames 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 screenlog_frames. 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.
screenlog_frames is provided by the Yaver MCP server (yaver-cli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.