mobile_hermes_reload

SERVERYaver SOURCEyaver-cli

High RISK CLASS

Category Execute

Parameters 30 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-hermes-reload.md

WHAT IT DOES

What mobile_hermes_reload does on Yaver

AI agents invoke mobile_hermes_reload 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
`mode`	string	—	Reload mode: "dev" (Metro fast-refresh, default) or "bundle" (push pre-built bundle).
`device_id`	string	—	Optional owned Yaver agent device id/name/alias that should perform the reload. Use this for remote boxes; target_device_id is only the receiving mobile SDK ses
`target_device_id`	string	—	Optional SDK device id to scope the broadcast to. Empty/omitted = broadcast to ALL subscribed devices. Used by the Path-C cross-device flow where Phone A drives

Parameters from the server's own tool schema.

RISK

Why mobile_hermes_reload is rated High

This tool executes a reload/rebuild operation on connected mobile devices with side effects that depend on the state of the codebase and development server. While not destructive (the reload is reversible), it actively triggers external operations (native rebuilds, hot reloads) on devices, which constitutes code execution in the Execute category.

From the tool's definition Tool triggers a 'hot-reload' or 'native_rebuild_required' command via SSE channel to connected SDK devices; performs POST /dev/reload with native-fingerprint delta computation and broadcasts commands to mobile devices under test.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

mobile_hermes_reload Rate-limited

mobile_hermes_reload 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_hermes_reload": {
      "limits": [
        {
          "counter": "mobile_hermes_reload_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_hermes_reload call is checked against it from then on.

FAQ

Questions about mobile_hermes_reload

What does the mobile_hermes_reload tool do? +

Trigger a Hermes hot-reload of the React Native / Expo app currently under test. Thin wrapper over POST /dev/reload — computes a native-fingerprint delta against the dev-server baseline and broadcasts a hot_reload (or native_rebuild_required) command via the BlackBox SSE channel to all connected SDK devices. Use this when an MCP client (Claude Code, glass-terminal vibe chip, ChatGPT) wants the app reloaded without an LLM round-trip. Returns { ok, changeClass: "js_only"|"native_rebuild_required"|"unknown", nativeChanges?, nativeChangesDetected }. 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_hermes_reload accept? +

mobile_hermes_reload accepts 3 parameters: mode, device_id, target_device_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on mobile_hermes_reload? +

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

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

Can I rate-limit mobile_hermes_reload? +

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

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

mobile_hermes_reload 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 645 Yaver tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

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