native_build

SERVERYaver SOURCEyaver-cli

High RISK CLASS

Category Execute

Parameters 91 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-kivanccakmak-yaver/native-build.md

WHAT IT DOES

What native_build does on Yaver

AI agents invoke native_build 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
`args`	array	—
`flavor`	string	—
`scheme`	string	—
`target`	string	—	device \| simulator \| testflight \| playstore \| local \| apk \| aab \| ipa
`platform`	string	Yes
`work_dir`	string	—	Repo root or project directory to scan.
`project_path`	string	—	Exact project path to use when work_dir is ambiguous.
`project_index`	integer	—	1-based index into the discovered candidates.
`install_on_device`	boolean	—

Parameters from the server's own tool schema.

RISK

Why native_build is rated High

The tool executes a build/install pipeline for native mobile apps. This is an Execute action because it runs code compilation and installs artifacts to target devices/systems. The blast radius is high: a malicious agent could build and install malware or backdoored apps, or exhaust resources with continuous builds.

From the tool's definition "Build or install a native iOS, Android, or Flutter app" — this triggers compilation and installation of mobile applications, which are external operations whose effects depend on arguments (target platform, project selection).

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs native_build 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 native_build, this is the rule to start with:

native_build Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "native_build": {
      "limits": [
        {
          "counter": "native_build_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about native_build

What does the native_build tool do? +

Build or install a native iOS, Android, or Flutter app. Yaver discovers matching mobile projects under work_dir (including mobile/, app/, apps/*, packages/*). If more than one candidate matches, it returns candidates instead of guessing. 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.

What parameters does native_build accept? +

native_build accepts 9 parameters: args, flavor, scheme, target, platform, work_dir, project_path, project_index, install_on_device. Required: platform. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on native_build? +

Register the Yaver MCP server in PolicyLayer and add a rule for native_build: 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.

What risk level is native_build? +

native_build is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit native_build? +

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

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

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

KEEP EXPLORING

More on Yaver, and thousands of servers like it.

This server

All 645 Yaver tools → High-risk tools on this server →

Across the catalogue

hook_native_function on Frida Game Hacking MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →