AI agents invoke head_tracking 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.
Based on the server context (physical robot control) and sibling tools (move_head, stop_motion), head_tracking likely activates a continuous tracking behavior on the robot's physical head, which constitutes executing an external/physical operation. The description is empty, lowering confidence.
From the tool's definition Tool name 'head_tracking' on a server that controls physical Reachy Mini robots with sibling tools like move_head, dance, play_emotion — implies triggering continuous physical motion tracking behavior on a robot.
Documented attack patterns abuse exactly the kind of access head_tracking 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 head_tracking:
{
"version": "1",
"default": "deny",
"tools": {
"head_tracking": {
"limits": [
{
"counter": "head_tracking_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}head_tracking 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.
head_tracking. 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 head_tracking: 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.
head_tracking 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 head_tracking 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 head_tracking. 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.
head_tracking 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.