robot_wake_up · Reachy Claude MCP: Risk & Policy

WHAT IT DOES

What robot_wake_up does on Reachy Claude MCP

AI agents invoke robot_wake_up to trigger actions in Reachy Claude MCP. 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.

WHY IT NEEDS A POLICY

Why robot_wake_up needs a policy

This tool executes a physical or simulated action (animation) on an external robotic system. It is not merely reading data or writing to a database; it triggers real-world or simulation-side effects (motor movements, speech, animations). The blast radius is medium because misuse could cause unexpected robot behavior but is unlikely to cause irreversible harm.

From the tool's definition Morning greeting animation with customizable message — triggers a physical animation on the Reachy Mini robot or its simulation

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

robot_wake_up Rate-limited

robot_wake_up 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": {
    "robot_wake_up": {
      "limits": [
        {
          "counter": "robot_wake_up_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about robot_wake_up

What does the robot_wake_up tool do? +

Morning greeting animation with customizable message. It is categorised as a Execute tool in the Reachy Claude MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on robot_wake_up? +

Register the Reachy Claude MCP server in PolicyLayer and add a rule for robot_wake_up: 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 Reachy Claude MCP. Nothing to install.

What risk level is robot_wake_up? +

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

Can I rate-limit robot_wake_up? +

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

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

robot_wake_up is provided by the Reachy Claude MCP server (mchardysam/reachy-claude-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.