This record as markdown: /tools/1shin-7-ya-frida-mcp/adb-push.md
What adb_push does on Ya Frida
AI agents use adb_push to create or update resources in Ya Frida, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ya Frida environment.
Why adb_push is rated Medium
This tool writes or modifies data on a connected Android device by transferring files from the local system. While not inherently destructive (files can be overwritten or deleted), the ability to push arbitrary files to a device—potentially system binaries, scripts, or configuration files—could enable code execution or system compromise if misused by an agent.
From the tool's definition adb_push: 'Push a local file or directory to the device.' The verb 'push' indicates uploading/writing data to a target device, and the description explicitly states it transfers local files to the device.
Attacks that exploit this kind of access
The rule that runs adb_push safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Ya Frida, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For adb_push, this is the rule to start with:
adb_push stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Ya Frida, apply this rule, and every adb_push call is checked against it from then on.
Questions about adb_push
Push a local file or directory to the device. It is categorised as a Write tool in the Ya Frida MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Ya Frida MCP server in PolicyLayer and add a rule for adb_push: 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 Ya Frida. Nothing to install.
adb_push is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the adb_push 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 adb_push. 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.
adb_push is provided by the Ya Frida MCP server (1shin-7/ya-frida-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Ya Frida, and thousands of servers like it.
This server
Across the catalogue