browser_screenshot_annotate
A read tool on the Termux Browser Pilot MCP server.
This record as markdown: /tools/salviz-termux-browser-pilot/browser-screenshot-annotate.md
What browser_screenshot_annotate does on Termux Browser Pilot
AI agents call browser_screenshot_annotate to retrieve information from Termux Browser Pilot without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why browser_screenshot_annotate is rated Low
A screenshot tool primarily reads/captures the current browser state (a Read operation). Annotation may involve writing overlay data, but the dominant action is capturing visual state. However, the description is empty, lowering confidence. Given the browser automation context, this tool likely captures and annotates a screenshot without side effects on the browser state itself.
From the tool's definition Tool name 'browser_screenshot_annotate' and empty description. Name suggests taking a screenshot and annotating it.
Attacks that exploit this kind of access
The rule that runs browser_screenshot_annotate safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Termux Browser Pilot, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For browser_screenshot_annotate, this is the rule to start with:
browser_screenshot_annotate is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Termux Browser Pilot, apply this rule, and every browser_screenshot_annotate call is checked against it from then on.
Questions about browser_screenshot_annotate
browser_screenshot_annotate is a read tool on the Termux Browser Pilot MCP server. It is categorised as a Read tool in the Termux Browser Pilot MCP Server, which means it retrieves data without modifying state.
Register the Termux Browser Pilot MCP server in PolicyLayer and add a rule for browser_screenshot_annotate: 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 Termux Browser Pilot. Nothing to install.
browser_screenshot_annotate 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 browser_screenshot_annotate 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 browser_screenshot_annotate. 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.
browser_screenshot_annotate is provided by the Termux Browser Pilot MCP server (salviz/termux-browser-pilot). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Termux Browser Pilot, and thousands of servers like it.
This server
Across the catalogue