mobile_project_status
Inspect whether a React Native / Expo project on this machine or an owned remote Yaver device is ready for Yaver iPhone/Android testing. Reports package manager, missing local tools, dependency-install state, Hermes compiler availability, and whether Hermes has been built before.
This record as markdown: /tools/io-github-kivanccakmak-yaver/mobile-project-status.md
What mobile_project_status does on Yaver
AI agents call mobile_project_status to retrieve information from Yaver without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
device_id | string | — | Optional owned Yaver device id/name/alias to inspect. |
directory | string | — | Project directory (default: agent work dir) |
Parameters from the server's own tool schema.
Why mobile_project_status is rated Low
This is a diagnostic/status-check tool that gathers information about local and remote Yaver device state. It reads and reports configuration and build readiness without creating, modifying, or deleting resources. Classification as Read is appropriate.
From the tool's definition The tool 'Inspect[s]' and 'Reports' on project state and readiness—it performs introspective queries (package manager, tools, dependencies, compiler status) without modifying data or executing code. No side effects described.
Risk signalsAccepts file system path (directory)
Attacks that exploit this kind of access
The rule that runs mobile_project_status 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_status, this is the rule to start with:
mobile_project_status is read-only, so it stays allowed. 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_status call is checked against it from then on.
Questions about mobile_project_status
Inspect whether a React Native / Expo project on this machine or an owned remote Yaver device is ready for Yaver iPhone/Android testing. Reports package manager, missing local tools, dependency-install state, Hermes compiler availability, and whether Hermes has been built before. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.
mobile_project_status 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_status: 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_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the mobile_project_status 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_status. 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_status 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.
This server
Across the catalogue