adb_pull_screenshot

Pull the captured screenshot into the workspace directory.

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-pull-screenshot.md

WHAT IT DOES

What adb_pull_screenshot does on LocalAnt

AI agents call adb_pull_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.

RISK

Why adb_pull_screenshot is rated Low

This tool reads and retrieves an existing screenshot from an Android device into the workspace. While it is a Read operation (no data is modified or deleted on the source), the severity is medium because screenshots can contain sensitive information (credentials, personal data, application state) that an autonomous agent could exfiltrate.

From the tool's definition Tool name 'adb_pull_screenshot' and description 'Pull the captured screenshot into the workspace directory' indicate it retrieves/extracts a screenshot artifact. The verb 'pull' denotes data retrieval without modification.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs adb_pull_screenshot safely

PolicyLayer is an MCP gateway: it sits between your AI agents and LocalAnt, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For adb_pull_screenshot, this is the rule to start with:

adb_pull_screenshot Allowed

adb_pull_screenshot is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "adb_pull_screenshot": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect LocalAnt, apply this rule, and every adb_pull_screenshot call is checked against it from then on.

FAQ

Questions about adb_pull_screenshot

What does the adb_pull_screenshot tool do? +

Pull the captured screenshot into the workspace directory. 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_pull_screenshot? +

Register the LocalAnt MCP server in PolicyLayer and add a rule for adb_pull_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_pull_screenshot? +

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

Can I rate-limit adb_pull_screenshot? +

Yes. Add a rate_limit block to the adb_pull_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_pull_screenshot completely? +

Set action: deny in the PolicyLayer policy for adb_pull_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_pull_screenshot? +

adb_pull_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.

KEEP EXPLORING

More on LocalAnt, and thousands of servers like it.

This server

All 216 LocalAnt tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →