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...
AI agents call primary_projects to retrieve information from Yaver without modifying anything — 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.
Even though primary_projects only reads data, uncontrolled read access leaks sensitive information and racks up API costs — an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
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.