Retrieves screenshot data for a specific annotation when visual context is needed to understand and implement the user\
AI agents call get_annotation_screenshot to retrieve information from Vibe Annotations Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Even though get_annotation_screenshot 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
Retrieves screenshot data for a specific annotation when visual context is needed to understand and implement the user\. It is categorised as a Read tool in the Vibe Annotations Server MCP Server, which means it retrieves data without modifying state.
Register the Vibe Annotations Server MCP server in PolicyLayer and add a rule for get_annotation_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 Vibe Annotations Server. Nothing to install.
get_annotation_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_annotation_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_annotation_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_annotation_screenshot is provided by the Vibe Annotations Server MCP server (vibe-annotations-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.