robot_oops · Reachy Claude MCP: Risk & Policy

WHAT IT DOES

What robot_oops does on Reachy Claude MCP

AI agents invoke robot_oops 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_oops needs a policy

This tool executes a physical action on a robot (or simulation), causing it to perform an 'oops' reaction animation. It spans the Execute category as it triggers an external operation on physical/simulated hardware. The blast radius is medium since misuse could cause unintended robot movements but is limited in scope.

From the tool's definition 'Show an oops reaction' — triggers a physical animation/emotion on the Reachy Mini robot or its simulation

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

robot_oops Rate-limited

robot_oops 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_oops": {
      "limits": [
        {
          "counter": "robot_oops_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_oops

What does the robot_oops tool do? +

Show an 'oops' reaction for mistakes or errors. 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_oops? +

Register the Reachy Claude MCP server in PolicyLayer and add a rule for robot_oops: 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_oops? +

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

Can I rate-limit robot_oops? +

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

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

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