Trigger a big celebration with dance and speech.
AI agents invoke robot_big_celebration 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.
This tool triggers an external operation (robot animation/dance and speech) that has real-world effects on a physical device. It falls under Execute rather than Write because it does not modify persistent data; instead, it runs a predefined routine on the robot.
From the tool's definition Tool name 'robot_big_celebration' and description 'Trigger a big celebration with dance and speech' indicate the tool executes external operations on the Reachy robot hardware, initiating physical movements and audio output whose effects depend on the robot's…
Attacks that exploit this kind of access
Trigger a big celebration with dance and speech. 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_big_celebration: 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_big_celebration 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_big_celebration 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_big_celebration. 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_big_celebration 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 →