Fetch all screen captures within a time range in chronological order.
AI agents call get_activity_timeline to retrieve information from Screen Memory without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only operation that retrieves historical screen capture data. While it is categorized as Read (retrieves data without side effects), the severity is elevated to high because the tool accesses and returns sensitive screen capture data that may contain passwords, personal information, financial details, or confidential business information visible on the user's screen during the specified…
From the tool's definition Tool description states it 'Fetch[es] all screen captures within a time range in chronological order.' This is a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
Fetch all screen captures within a time range in chronological order. It is categorised as a Read tool in the Screen Memory MCP Server, which means it retrieves data without modifying state.
Register the Screen Memory MCP server in PolicyLayer and add a rule for get_activity_timeline: 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 Screen Memory. Nothing to install.
get_activity_timeline 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_activity_timeline 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_activity_timeline. 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_activity_timeline is provided by the Screen Memory MCP server (yonglim2392/screen-memory-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 →