gateway_node_apps · Yaver MCP: Risk & Policy

WHAT IT DOES

What gateway_node_apps does on Yaver

AI agents use gateway_node_apps 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.

PARAMETERS

Parameter	Type	Required	Description
`node`	string	Yes	Device node id (the adb serial of the redroid/phone)

Parameters from the server's own tool schema.

WHY IT NEEDS A POLICY

Why gateway_node_apps needs a policy

An AI agent can call gateway_node_apps 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

Recommended rule Ready

Verdict

gateway_node_apps Rate-limited

gateway_node_apps stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "gateway_node_apps": {
      "limits": [
        {
          "counter": "gateway_node_apps_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Yaver, so you can run agents against it safely.

FAQ

Questions about gateway_node_apps

What does the gateway_node_apps tool do? +

Personal Agent Gateway: list the DESIRED app-set for a device node (redroid or a real phone) plus which of those apps are currently installed. The desired set is local-only (~/.yaver/nodes/<node>/apps.json) — never Convex. Provisioning only: install ≠ logged in. 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.

What parameters does gateway_node_apps accept? +

gateway_node_apps accepts 1 parameter: node. Required: node. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on gateway_node_apps? +

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

gateway_node_apps is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit gateway_node_apps? +

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

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

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