push_android
Discover an Android-capable project, build an AAB with the correct stack-specific builder, wait for completion, then upload it to Google Play internal testing.
This record as markdown: /tools/io-github-kivanccakmak-yaver/push-android.md
What push_android does on Yaver
AI agents invoke push_android to trigger actions in Yaver. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
flavor | string | — | |
work_dir | string | — | |
project_path | string | — | |
project_index | integer | — |
Parameters from the server's own tool schema.
Why push_android is rated High
This tool triggers a multi-step external operation: it discovers a project, executes a build process, and uploads the resulting artifact to Google Play internal testing. These are external operations with real-world side effects (publishing to an app store), making Execute the appropriate category.
From the tool's definition build an AAB with the correct stack-specific builder, wait for completion, then upload it to Google Play internal testing
Attacks that exploit this kind of access
The rule that runs push_android safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Yaver, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For push_android, this is the rule to start with:
push_android stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Yaver, apply this rule, and every push_android call is checked against it from then on.
Questions about push_android
Discover an Android-capable project, build an AAB with the correct stack-specific builder, wait for completion, then upload it to Google Play internal testing. It is categorised as a Execute tool in the Yaver MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
push_android accepts 4 parameters: flavor, work_dir, project_path, project_index. The full parameter table on this page comes from the server's own tool schema.
Register the Yaver MCP server in PolicyLayer and add a rule for push_android: 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 Yaver. Nothing to install.
push_android is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the push_android 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 push_android. 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.
push_android is provided by the Yaver MCP server (yaver-cli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Yaver, and thousands of servers like it.
Across the catalogue