move_robot_linear · Universal Robot MCP Server MCP

WHAT IT DOES

What move_robot_linear does on Universal Robot MCP Server

AI agents invoke move_robot_linear to trigger actions in Universal Robot 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.

WHY IT NEEDS A POLICY

Why move_robot_linear needs a policy

Linear motion control of a physical robot arm is an Execute-category action with critical severity. Even with collision detection, misuse could cause physical harm to people, damage equipment, or destroy workpieces. The empty description lowers confidence slightly, but the server context makes the tool's physical actuation nature clear.

From the tool's definition Tool name 'move_robot_linear' on a server described as controlling Universal Robots with 'precise joint/linear motion control' and 'built-in collision detection'

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

move_robot_linear Rate-limited

move_robot_linear 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_linear": {
      "limits": [
        {
          "counter": "move_robot_linear_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 Universal Robot MCP Server, so you can run agents against it safely.

FAQ

Questions about move_robot_linear

What does the move_robot_linear tool do? +

move_robot_linear. It is categorised as a Execute tool in the Universal Robot MCP Server 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_linear? +

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

What risk level is move_robot_linear? +

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

Can I rate-limit move_robot_linear? +

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

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

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

// THE FULL RECORD

move_robot_linear is one line of Universal Robot MCP Server's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →