List all captured screenshots with their IDs and timestamps.
AI agents call list_screenshots to retrieve information from Zoho Timeline MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves metadata about previously captured screenshots (IDs and timestamps) but does not create, modify, delete, or execute any operations. It is a pure data retrieval function with no side effects, fitting the Read category. Severity is low because viewing a list of local screenshots poses minimal security risk even if misused.
From the tool's definition Tool name 'list_screenshots' and description 'List all captured screenshots with their IDs and timestamps' indicate a retrieval operation that queries existing data without modification or side effects.
Attacks that exploit this kind of access
List all captured screenshots with their IDs and timestamps. It is categorised as a Read tool in the Zoho Timeline MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Zoho Timeline MCP Server MCP server in PolicyLayer and add a rule for list_screenshots: 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 Zoho Timeline MCP Server. Nothing to install.
list_screenshots 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 list_screenshots 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 list_screenshots. 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.
list_screenshots is provided by the Zoho Timeline MCP Server MCP server (johnelamont/zoho-timeline-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 →