move_to · Nova Control MCP: Risk & Policy

WHAT IT DOES

What move_to does on Nova Control

AI agents invoke move_to to trigger actions in Nova Control. 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_to needs a policy

This tool commands physical hardware (servos on a robot) to move to specified positions. It executes an external physical operation whose effects depend on the target position arguments. While not destructive in a data sense, misuse could cause physical harm or damage to the robot or surroundings, warranting medium severity.

From the tool's definition 'move one or more servos smoothly to their target positions' — triggers physical actuation of servo motors on a robot

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

move_to Rate-limited

move_to 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_to": {
      "limits": [
        {
          "counter": "move_to_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 Nova Control, so you can run agents against it safely.

FAQ

Questions about move_to

What does the move_to tool do? +

move one or more servos smoothly to their target positions,. It is categorised as a Execute tool in the Nova Control 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_to? +

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

What risk level is move_to? +

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

Can I rate-limit move_to? +

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

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

move_to is provided by the Nova Control MCP server (nova-control-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.