mobile_platform_matrix
Return the source-of-truth platform surface matrix for mobile, TV, watch, car, and AR/VR deployability across Apple and Android. Includes what is ready, build-only, bundled into another artifact, blocked by entitlement/review work, and which release validation drivers are supported, including dee...
This record as markdown: /tools/io-github-kivanccakmak-yaver/mobile-platform-matrix.md
What mobile_platform_matrix does on Yaver
AI agents call mobile_platform_matrix 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 | — | Repo root. Empty = current yaver repo or current working directory. |
Parameters from the server's own tool schema.
Why mobile_platform_matrix is rated Low
This tool queries and returns static or semi-static platform metadata about deployability, build status, and validation support. It has no side effects, does not modify state, execute code, delete data, or commit financial obligations. It is a straightforward information retrieval tool with minimal security risk, hence low severity.
From the tool's definition Returns the source-of-truth platform surface matrix for mobile, TV, watch, car, and AR/VR deployability across Apple and Android.
Risk signalsAccepts file system path (directory)
Attacks that exploit this kind of access
The rule that runs mobile_platform_matrix 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_platform_matrix, this is the rule to start with:
mobile_platform_matrix 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_platform_matrix call is checked against it from then on.
Questions about mobile_platform_matrix
Return the source-of-truth platform surface matrix for mobile, TV, watch, car, and AR/VR deployability across Apple and Android. Includes what is ready, build-only, bundled into another artifact, blocked by entitlement/review work, and which release validation drivers are supported, including deep-build-doctor and autotest-selenium/WebDriver. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.
mobile_platform_matrix 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_platform_matrix: 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_platform_matrix 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_platform_matrix 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_platform_matrix. 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_platform_matrix 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