mobile_test_open

SERVERYaver SOURCEyaver-cli

High RISK CLASS

Category Execute

Parameters 40 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-kivanccakmak-yaver/mobile-test-open.md

WHAT IT DOES

What mobile_test_open does on Yaver

AI agents invoke mobile_test_open to trigger actions in Yaver. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

Parameter	Type	Required	Description
`url`	string	—	Mobile web URL. Default http://localhost:8081 (Metro).
`mode`	string	—	open = headed window for a human (default). verify = headless closed-loop assertion.
`profile`	string	—	Persistent profile for mode=open. Default ~/.yaver-e2e-profile; use a fresh one when the default is locked by another Chromium instance.
`timeout_sec`	integer	—	Max seconds to wait (verify mode, and Metro start in open mode). Default 180.

Parameters from the server's own tool schema.

RISK

Why mobile_test_open is rated High

Tool executes browser automation and E2E test scripts with real viewport and headless modes.

From the tool's definition launches a headed Chromium window; runs headless closed-loop assertion

Risk signalsAccepts URL/endpoint input (url)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs mobile_test_open 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_test_open, this is the rule to start with:

mobile_test_open Rate-limited

mobile_test_open stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "mobile_test_open": {
      "limits": [
        {
          "counter": "mobile_test_open_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Yaver, apply this rule, and every mobile_test_open call is checked against it from then on.

FAQ

Questions about mobile_test_open

What does the mobile_test_open tool do? +

Open the Yaver mobile app (RN-web) for testing at a REAL mobile viewport. mode=open (default) launches a headed Chromium window at iPhone 13 viewport with touch + a persistent profile so a human can sign in and test; mode=verify runs the headless closed-loop assertion that the task-detail LiveConsoleSection rendered the streamed opencode console (e2e/verify_live_console.mjs). Ensures Metro is up first. Never substitute a narrowed desktop Chrome window for the mobile app — RN-web renders a different component tree without the device context (AGENTS.md viewport rule). It is categorised as a Execute tool in the Yaver MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

What parameters does mobile_test_open accept? +

mobile_test_open accepts 4 parameters: url, mode, profile, timeout_sec. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on mobile_test_open? +

Register the Yaver MCP server in PolicyLayer and add a rule for mobile_test_open: 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.

What risk level is mobile_test_open? +

mobile_test_open is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit mobile_test_open? +

Yes. Add a rate_limit block to the mobile_test_open 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.

How do I block mobile_test_open completely? +

Set action: deny in the PolicyLayer policy for mobile_test_open. 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.

What MCP server provides mobile_test_open? +

mobile_test_open 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.

KEEP EXPLORING

More on Yaver, and thousands of servers like it.

This server

All 678 Yaver tools → High-risk tools on this server →

Across the catalogue

execute_test_case on Percepta MCP Server → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →