move_robot · SO-ARM100 Robot Control MCP: Risk & Policy

WHAT IT DOES

What move_robot does on SO-ARM100 Robot Control MCP

AI agents invoke move_robot to trigger actions in SO-ARM100 Robot Control 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.

WHY IT NEEDS A POLICY

Why move_robot needs a policy

Despite the empty description, the tool name and server context strongly imply this tool commands physical robot movement. Executing physical robot motion can cause real-world harm (collisions, injury, equipment damage), making this an Execute-category tool with high severity. Confidence is slightly reduced due to the lack of a description.

From the tool's definition Tool name 'move_robot' on a server explicitly designed to 'control SO-ARM100 and LeKiwi robots'; sibling tools include 'control_gripper' and 'move_rover' confirming physical actuation context.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

move_robot Rate-limited

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

View as policy code

policy.json

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

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches SO-ARM100 Robot Control MCP, so you can run agents against it safely.

FAQ

Questions about move_robot

What does the move_robot tool do? +

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

How do I enforce a policy on move_robot? +

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

What risk level is move_robot? +

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

Can I rate-limit move_robot? +

Yes. Add a rate_limit block to the move_robot 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 move_robot completely? +

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

move_robot is provided by the SO-ARM100 Robot Control MCP server (yunis147/mcp_robot). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.