mobile_project_prepare · Yaver MCP: Risk & Policy

WHAT IT DOES

What mobile_project_prepare does on Yaver

AI agents use mobile_project_prepare to create or update resources in Yaver — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Yaver environment.

PARAMETERS

Parameter	Type	Required	Description
`device_id`	string	—	Optional owned Yaver device id/name/alias to prepare.
`directory`	string	—	Project directory (default: agent work dir)

Parameters from the server's own tool schema.

WHY IT NEEDS A POLICY

Why mobile_project_prepare needs a policy

An AI agent can call mobile_project_prepare faster than any human can review — one bad instruction and it creates or modifies resources in Yaver by the hundred, each call as confident as the last.

Risk signalsAccepts file system path (directory)

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

mobile_project_prepare Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "mobile_project_prepare": {
      "limits": [
        {
          "counter": "mobile_project_prepare_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Yaver, so you can run agents against it safely.

FAQ

Questions about mobile_project_prepare

What does the mobile_project_prepare tool do? +

Prepare a fresh React Native / Expo clone on this machine or an owned remote Yaver device by auto-installing project dependencies when the machine has the right package manager available. Returns readiness fields after the install attempt. It is categorised as a Write tool in the Yaver MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does mobile_project_prepare accept? +

mobile_project_prepare accepts 2 parameters: device_id, directory. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on mobile_project_prepare? +

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

mobile_project_prepare is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit mobile_project_prepare? +

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

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

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