New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

runtime_control

Send a control action (tap/swipe/pinch/navigate/text/key) to a remote-runtime session — the seam a runner uses to browse the app, not just the code.

SERVERYaver SOURCEyaver-cli
High RISK CLASS
Category Execute
Parameters 112 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/runtime-control.md

What runtime_control does on Yaver

AI agents invoke runtime_control 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.

ParameterTypeRequiredDescription
x integer —
y integer —
x2 integer — Swipe end-point x.
y2 integer — Swipe end-point y.
key string —
url string — Target URL for action=navigate. http/https only. For browser-window this is the ONLY way to show content — the window opens at about:blank.
text string —
scale number — Pinch scale centred on x,y: >1 zooms in (fingers apart), <1 zooms out. Only used by action=pinch|zoom.
action string Yes tap | swipe | pinch | zoom | navigate | text | key
sessionId string Yes
durationMs integer — Swipe or pinch duration in ms.

Parameters from the server's own tool schema.

Why runtime_control is rated High

Executes UI interactions on a remote device session, enabling arbitrary app control.

From the tool's definition Send a control action (tap/swipe/pinch/navigate/text/key) to a remote-runtime session

Risk signalsAccepts URL/endpoint input (url) · High parameter count (11 properties)

Questions about runtime_control

What does the runtime_control tool do? +

Send a control action (tap/swipe/pinch/navigate/text/key) to a remote-runtime session — the seam a runner uses to browse the app, not just the code. 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 runtime_control accept? +

runtime_control accepts 11 parameters: x, y, x2, y2, key, url, text, scale, action, sessionId, durationMs. Required: action, sessionId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on runtime_control? +

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

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

Can I rate-limit runtime_control? +

Yes. Add a rate_limit block to the runtime_control 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 runtime_control completely? +

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

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

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Yaver's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.