mobile_project_actions_audit
Snowball guard for the mobile Projects surface: verifies every discovered mobile-capable project card has at least one supported operation (Hot Reload, Remote Runtime, or build). Catches the false-green class where inventory says a project exists but tapping it produces no runnable action. Option...
This record as markdown: /tools/io-github-kivanccakmak-yaver/mobile-project-actions-audit.md
What mobile_project_actions_audit does on Yaver
AI agents call mobile_project_actions_audit 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 |
|---|---|---|---|
directory | string | — | Optional project/workspace directory to audit. Empty = all discovered mobile projects. |
Parameters from the server's own tool schema.
Why mobile_project_actions_audit is rated Low
This tool audits/verifies the state of mobile project configurations by checking that projects have supported operations. It reads and inspects existing project data without modifying, executing, or deleting anything. The optional directory parameter restricts the scope of reading. No side effects are indicated.
From the tool's definition verifies every discovered mobile-capable project card has at least one supported operation... Catches the false-green class where inventory says a project exists but tapping it produces no runnable action
Risk signalsAccepts file system path (directory) · Bulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs mobile_project_actions_audit 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_actions_audit, this is the rule to start with:
mobile_project_actions_audit 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_actions_audit call is checked against it from then on.
Questions about mobile_project_actions_audit
Snowball guard for the mobile Projects surface: verifies every discovered mobile-capable project card has at least one supported operation (Hot Reload, Remote Runtime, or build). Catches the false-green class where inventory says a project exists but tapping it produces no runnable action. Optional directory restricts the audit to that path/prefix. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.
mobile_project_actions_audit accepts 1 parameter: 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_actions_audit: 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_actions_audit 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_actions_audit 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_actions_audit. 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_actions_audit 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