runtime_create
Create a remote-runtime session (boot the sim/emulator and hold it addressable). Returns the session id + selected target + first-frame availability.
This record as markdown: /tools/io-github-kivanccakmak-yaver/runtime-create.md
What runtime_create does on Yaver
AI agents invoke runtime_create 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 |
|---|---|---|---|
workDir | string | Yes | |
targetId | string | Yes | e.g. ios-simulator, watchos-simulator, android-emulator, browser-window. |
framework | string | Yes | |
realDeviceId | string | — | Opaque id returned by real_device_probe. Required to select an exact physical device when targetId=android-device. |
transportMode | string | — | direct-webrtc (default) or relay-jpeg-poll. |
Parameters from the server's own tool schema.
Why runtime_create is rated High
Boots a remote simulator/emulator session, triggering external compute resources.
From the tool's definition Create a remote-runtime session, boot the sim/emulator
Attacks that exploit this kind of access
The rule that runs runtime_create 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 runtime_create, this is the rule to start with:
runtime_create 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Yaver, apply this rule, and every runtime_create call is checked against it from then on.
Questions about runtime_create
Create a remote-runtime session (boot the sim/emulator and hold it addressable). Returns the session id + selected target + first-frame availability. 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.
runtime_create accepts 5 parameters: workDir, targetId, framework, realDeviceId, transportMode. Required: workDir, targetId, framework. 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 runtime_create: 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.
runtime_create is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the runtime_create 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 runtime_create. 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.
runtime_create 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.
Across the catalogue