Pull all screen recordings from device to local directory
AI agents call pull_recordings to retrieve information from Enhanced ADB 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/copies screen recording files from an Android device to a local directory. It is a read operation that queries and transfers existing data without side effects on the device state. No data is modified, deleted, or executed. The copying operation is reversible and non-destructive.
From the tool's definition Tool name is 'pull_recordings' and description states it 'Pull[s] all screen recordings from device to local directory' — a retrieval operation with no modification or deletion of source data.
Attacks that exploit this kind of access
Pull all screen recordings from device to local directory. It is categorised as a Read tool in the Enhanced ADB MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Enhanced ADB MCP Server MCP server in PolicyLayer and add a rule for pull_recordings: 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 Enhanced ADB MCP Server. Nothing to install.
pull_recordings 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 pull_recordings 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 pull_recordings. 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.
pull_recordings is provided by the Enhanced ADB MCP Server MCP server (rahulkr/r_adb_mcp_server). 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 →