primary_projects
List projects discovered by the agent's filesystem scanner on the user's primary remote device. Pass mobile_only=true to filter to mobile-capable projects only (Expo / React Native / Flutter / Swift / Kotlin) — same as yaver primary mobiles. Discovery runs without any coding-agent installed on th...
This record as markdown: /tools/io-github-kivanccakmak-yaver/primary-projects.md
What primary_projects does on Yaver
AI agents call primary_projects 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 |
|---|---|---|---|
mobile_only | boolean | — | When true, return only mobile-capable projects (mobile + Flutter + Swift + Kotlin). |
Parameters from the server's own tool schema.
Why primary_projects is rated Low
The primary_projects tool performs discovery and enumeration of existing projects on the user's primary device filesystem. It filters and lists data without creating, modifying, deleting, or executing code. The optional mobile_only parameter is a filter, not an action trigger.
From the tool's definition Tool description states 'List projects discovered by the agent's filesystem scanner' — a read-only query operation that retrieves information about projects on the user's device. No modification, deletion, or external execution is implied.
Attacks that exploit this kind of access
The rule that runs primary_projects 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 primary_projects, this is the rule to start with:
primary_projects 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 primary_projects call is checked against it from then on.
Questions about primary_projects
List projects discovered by the agent's filesystem scanner on the user's primary remote device. Pass mobile_only=true to filter to mobile-capable projects only (Expo / React Native / Flutter / Swift / Kotlin) — same as yaver primary mobiles. Discovery runs without any coding-agent installed on the box. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.
primary_projects accepts 1 parameter: mobile_only. 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 primary_projects: 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.
primary_projects 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 primary_projects 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 primary_projects. 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.
primary_projects 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