unitree_out_and_back

THE RISK

High Risk

Why unitree_out_and_back needs a policy

This tool is on a server explicitly designed to control Unitree robots with hardware backends. The name 'out_and_back' suggests a physical movement routine (move out and return). Physical robot actuation can cause real-world harm (collisions, injury) making it high severity.

From the tool's definition Tool name 'unitree_out_and_back' on a robot-control server; description is empty/uninformative.

Documented attack patterns abuse exactly the kind of access unitree_out_and_back gives an agent:

POLICY

How to control unitree_out_and_back

PolicyLayer is an MCP gateway — it sits between your AI agents and Robot, and nothing reaches the server without passing your rules. This is the rule we recommend for unitree_out_and_back:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "unitree_out_and_back": {
      "limits": [
        {
          "counter": "unitree_out_and_back_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

unitree_out_and_back 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.

Create a free account and register Robot — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RATE-LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Robot tools

Destructive dji_disconnect dji_disconnect Execute dji_emergency_stop dji_emergency_stop Execute emergency_stop_all emergency_stop_all Execute run_routine_sequence run_routine_sequence Execute unitree_stop unitree_stop Execute dji_land dji_land Execute dji_perimeter_scan dji_perimeter_scan Execute dji_takeoff dji_takeoff

All 24 Robot tools →

Execute tools on other servers

Android Forensics ADB MCP Server adb_shell_command EMBA-MCP run_emba_scan Frida Game Hacking MCP remove_breakpoint Procmon request_elevation

Go deeper

High-risk tools in Robot → Every high-risk tool this server exposes, in one view.
All high-risk MCP tools → Every high-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Agent sandbox → Bounding what an agent can execute and where the boundary should sit.
Least privilege for MCP → Granting agents the minimum tool surface the task needs.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about unitree_out_and_back

What does the unitree_out_and_back tool do? +

unitree_out_and_back. It is categorised as a Execute tool in the Robot MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on unitree_out_and_back? +

Register the Robot MCP server in PolicyLayer and add a rule for unitree_out_and_back: 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 Robot. Nothing to install.

What risk level is unitree_out_and_back? +

unitree_out_and_back is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit unitree_out_and_back? +

Yes. Add a rate_limit block to the unitree_out_and_back 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.

How do I block unitree_out_and_back completely? +

Set action: deny in the PolicyLayer policy for unitree_out_and_back. 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.

What MCP server provides unitree_out_and_back? +

unitree_out_and_back is provided by the Robot MCP server (showkeyjar/robot-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Robot tool call.

Start from Robot, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →