// SCAN REPORT

SO-ARM100 Robot Control MCP

5 tools. 3 can modify or destroy data without limits.

3 write tools that can modify data. Rate limits recommended.

Last updated: 3 Jul 2026

3 can modify or destroy data

2 read-only

5 tools total

Community server · catalogue entry verified 03/07/2026

How to control SO-ARM100 Robot Control MCP ↓

TOOL MAP

What SO-ARM100 Robot Control MCP exposes to your agents

Read (2) Write / Execute (3) Destructive / Financial (0)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

High Risk

The most dangerous SO-ARM100 Robot Control MCP tools

Execute · High move_robot Despite the empty description, the tool name and server context strongly imply this tool commands physical robot movement. Execute · High move_rover The tool name 'move_rover' strongly implies physical actuation of a robot rover. Execute · High control_gripper Controlling a physical robot gripper is an Execute-category action — it triggers an external physical operation whose effects depend on arguments (e.g., open/close, grip force).

3 of SO-ARM100 Robot Control MCP's 5 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control SO-ARM100 Robot Control MCP

PolicyLayer is an MCP gateway — it sits between your AI agents and SO-ARM100 Robot Control MCP, and nothing reaches the server without passing your rules. These are the rules we recommend:

Cap read operations

{
  "get_initial_instructions": {
    "limits": [
      {
        "counter": "get_initial_instructions_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register SO-ARM100 Robot Control MCP — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON SO-ARM100 ROBOT CONTROL →

Instant setup, no code required.

FULL CATALOGUE

All 5 SO-ARM100 Robot Control MCP tools

EXECUTE 3 tools

Execute control_gripper Control the robot Execute move_robot move_robot Execute move_rover move_rover

READ 2 tools

Read get_initial_instructions Get a description of the robot and instructions for the user. Run it before using any other tool. Read get_robot_state Get current robot state with images from all cameras. Returns list of objects: json with results of the move a

FAQ

Questions about SO-ARM100 Robot Control MCP

Is the SO-ARM100 Robot Control MCP server safe to use without restrictions? +

The SO-ARM100 Robot Control MCP server is primarily read-only with 2 read tools. While it cannot modify data, an agent in a retry loop can make thousands of API calls per minute, exhausting rate limits and running up costs. Rate limiting is still recommended.

How many tools does the SO-ARM100 Robot Control MCP server expose? +

5 tools across 2 categories: Read, Write. 2 are read-only. 3 can modify, create, or delete data.

How do I enforce a policy on SO-ARM100 Robot Control MCP? +

Register the SO-ARM100 Robot Control MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every SO-ARM100 Robot Control MCP tool call.

Deterministic rules across all 5 SO-ARM100 Robot Control MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON SO-ARM100 ROBOT CONTROL →

Instant setup, no code required.

5 SO-ARM100 Robot Control MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.