mobile_project_prepare
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.
This record as markdown: /tools/io-github-kivanccakmak-yaver/mobile-project-prepare.md
What mobile_project_prepare does on Yaver
AI agents invoke mobile_project_prepare 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 |
|---|---|---|---|
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 mobile_project_prepare is rated High
This tool executes shell-level package manager commands to install dependencies on a machine or remote device. It triggers external operations whose effects depend on the project and environment, placing it in the Execute category. Severity is medium because it modifies the filesystem and can pull arbitrary third-party packages, but it is scoped to a project directory and is generally reversible.
From the tool's definition 'auto-installing project dependencies' and 'install attempt' — the tool runs package manager commands (e.g., npm install, yarn, expo install) on the local machine or a remote device
Risk signalsAccepts file system path (directory)
Attacks that exploit this kind of access
The rule that runs mobile_project_prepare 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 mobile_project_prepare, this is the rule to start with:
mobile_project_prepare 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 mobile_project_prepare call is checked against it from then on.
Questions about mobile_project_prepare
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 Execute tool in the Yaver MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
mobile_project_prepare accepts 2 parameters: device_id, directory. 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 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.
mobile_project_prepare 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 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.
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.
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.
More on Yaver, and thousands of servers like it.
Across the catalogue