robot_dance_respond
AI agents invoke robot_dance_respond 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.
Based on the tool name and server context, this tool likely triggers a physical dance animation on the Reachy Mini robot or its simulation. This constitutes executing an external physical/hardware operation. The empty description lowers confidence significantly. Severity is medium because misuse could cause unexpected physical robot movements.
From the tool's definition Tool name 'robot_dance_respond' and server context of controlling a physical robot with 'celebratory animations' and 'emotions'. Description is empty/uninformative.
Attacks that exploit this kind of access
robot_dance_respond. 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.
Register the Reachy Claude MCP server in PolicyLayer and add a rule for robot_dance_respond: 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.
robot_dance_respond is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the robot_dance_respond 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.
Set action: deny in the PolicyLayer policy for robot_dance_respond. 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.
robot_dance_respond 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →