Personal Agent Gateway: PROVISION a device node — list the apps you want once and Yaver installs them all (no one-by-one). Reconciles the desired app-set onto the node: already-present apps are skipped, missing apps are installed Play-sourced (NEVER a sideloaded APK), Play blocks/region-locks are...
AI agents use gateway_node_sync to create or update resources in Yaver — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Yaver environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
apps | array | — | Desired apps to set + sync. Each: {packageId, required?}. Omit to reconcile the node's stored desired set. |
mode | string | — | Install path: 'play_ui' (default, drives the Play Store UI) or 'device_owner' (silent install — needs the node enrolled as a managed device). |
node | string | Yes | Device node id (adb serial) |
Parameters from the server's own tool schema.
An AI agent can call gateway_node_sync faster than any human can review — one bad instruction and it creates or modifies resources in Yaver by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
Personal Agent Gateway: PROVISION a device node — list the apps you want once and Yaver installs them all (no one-by-one). Reconciles the desired app-set onto the node: already-present apps are skipped, missing apps are installed Play-sourced (NEVER a sideloaded APK), Play blocks/region-locks are recorded as 'unavailable' and STOPPED on (never evaded). Returns per-app status. install ≠ logged in — authorize each app via the gateway login broker separately afterwards. It is categorised as a Write tool in the Yaver MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
gateway_node_sync accepts 3 parameters: apps, mode, node. Required: node. 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 gateway_node_sync: 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.
gateway_node_sync is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the gateway_node_sync 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 gateway_node_sync. 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.
gateway_node_sync 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.