AI agents invoke show to trigger actions in Reachy Mini 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.
Given the server context (Reachy Mini robot control with emotional expressions and motor commands) and sibling tools that are all physical/sensory robot actions, 'show' likely triggers a physical robot action such as displaying an emotion or expression. This constitutes Execute-level risk as it causes external physical operation. Confidence is lowered due to empty description.
From the tool's definition Tool name 'show' on a robot control server with sibling tools including 'speak', 'look', 'snap', 'rest', 'listen' — suggests triggering a physical robot action (e.g., displaying an expression or visual output on the robot).
Documented attack patterns abuse exactly the kind of access show gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Reachy Mini MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for show:
{
"version": "1",
"default": "deny",
"tools": {
"show": {
"limits": [
{
"counter": "show_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}show 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.
show. It is categorised as a Execute tool in the Reachy Mini MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Reachy Mini MCP server in PolicyLayer and add a rule for show: 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. Nothing to install.
show 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 show 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 show. 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.
show is provided by the Reachy Mini MCP server (jackccrawford/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, 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.
7 Reachy Mini MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.