mobile_hermes_doctor

SERVERYaver SOURCEyaver-cli

High RISK CLASS

Category Execute

Parameters 40 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-doctor.md

WHAT IT DOES

What mobile_hermes_doctor does on Yaver

AI agents invoke mobile_hermes_doctor 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
`device_id`	string	—	Optional owned Yaver agent device id/name/alias that should run the diagnosis. Hermes doctoring inspects a CHECKOUT, so the honest answer comes from the machine
`directory`	string	—	Project or monorepo directory (default: agent work dir)
`availableModules`	array	—	Optional native module names reported by the paired Yaver mobile runtime
`availableModuleMap`	object	—	Optional native module name to version map from the paired Yaver mobile runtime

Parameters from the server's own tool schema.

RISK

Why mobile_hermes_doctor is rated High

This tool orchestrates a complex diagnostic and build workflow for mobile development. While primarily diagnostic (checking states), its core function is to trigger external build and reload operations on a mobile device via Yaver. The side effects—code compilation, app reloading, dependency installation—depend on tool arguments and project context, making it Execute rather than Read.

From the tool's definition Tool description states it 'checks local tools, dependency install state, Hermes compiler readiness, prior bundle state, and native-module compatibility, then returns the exact MCP next actions to prepare/build before reloading'.

Risk signalsAccepts file system path (directory)

Attacks that exploit this kind of access

RECOMMENDED RULE

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

mobile_hermes_doctor Rate-limited

mobile_hermes_doctor 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_doctor": {
      "limits": [
        {
          "counter": "mobile_hermes_doctor_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_doctor call is checked against it from then on.

FAQ

Questions about mobile_hermes_doctor

What does the mobile_hermes_doctor tool do? +

Agent-friendly doctor for the common React Native / Expo phone reload path. Resolves the mobile project inside a monorepo, checks local tools, dependency install state, Hermes compiler readiness, prior bundle state, and native-module compatibility, then returns the exact MCP next actions to prepare/build before reloading in Yaver mobile. 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_doctor accept? +

mobile_hermes_doctor accepts 4 parameters: device_id, directory, availableModules, availableModuleMap. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on mobile_hermes_doctor? +

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

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

Can I rate-limit mobile_hermes_doctor? +

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

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

mobile_hermes_doctor 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 →