New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

adb_screenshot

Capture a screenshot to the device and report the path.

SERVERLocalAnt SOURCEyuga-hashimoto/localant
Low RISK CLASS
Category Read
Parameters 00 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/yuga-hashimoto-localant/adb-screenshot.md

What adb_screenshot does on LocalAnt

AI agents call adb_screenshot to retrieve information from LocalAnt without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why adb_screenshot is rated Low

This tool reads/retrieves the current visual state of the device screen and returns a file path. It has no side effects on the device state, system data, or user files—it is purely observational. A screenshot can inform an AI agent but cannot directly harm the system. Severity is low because the blast radius of misuse is limited to potential privacy leakage of what is visible on screen, not system compromise.

From the tool's definition Tool description states it 'Capture a screenshot to the device and report the path' — captures visual data with no modification or destructive action.

Questions about adb_screenshot

What does the adb_screenshot tool do? +

Capture a screenshot to the device and report the path. It is categorised as a Read tool in the LocalAnt MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on adb_screenshot? +

Register the LocalAnt MCP server in PolicyLayer and add a rule for adb_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 LocalAnt. Nothing to install.

What risk level is adb_screenshot? +

adb_screenshot is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit adb_screenshot? +

Yes. Add a rate_limit block to the adb_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.

How do I block adb_screenshot completely? +

Set action: deny in the PolicyLayer policy for adb_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.

What MCP server provides adb_screenshot? +

adb_screenshot is provided by the LocalAnt MCP server (yuga-hashimoto/localant). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on LocalAnt, and thousands of servers like it.

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of LocalAnt's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.