AI agents invoke stop_motion to trigger actions in Reachy Mini MCP Server. 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.
stop_motion most likely stops or halts motion sequences on the Reachy Mini robot. While the description is empty (lowering confidence slightly), the context—a robot control server with tools for head movement, choreographed dances, and emotion animations—indicates this triggers an external operation that changes robot state.
From the tool's definition Tool name 'stop_motion' on a robot control server (Reachy Mini) that exposes motion manipulation capabilities alongside 'move_head', 'dance', 'play_emotion', and 'speak'. The tool operates a physical robotic system.
Documented attack patterns abuse exactly the kind of access stop_motion gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Reachy Mini MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for stop_motion:
{
"version": "1",
"default": "deny",
"tools": {
"stop_motion": {
"limits": [
{
"counter": "stop_motion_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}stop_motion 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.
Free to start. No card required.
stop_motion. It is categorised as a Execute tool in the Reachy Mini MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Reachy Mini MCP Server MCP server in PolicyLayer and add a rule for stop_motion: 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 Mini MCP Server. Nothing to install.
stop_motion 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 stop_motion 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 stop_motion. 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.
stop_motion is provided by the Reachy Mini MCP Server MCP server (pixelml/reachy-mini-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Reachy Mini MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
8 Reachy Mini MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.