station.add_robot · RoboDK MCP Server MCP: Risk & Policy

WHAT IT DOES

What station.add_robot does on RoboDK MCP Server

AI agents use station.add_robot to create or update resources in RoboDK MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your RoboDK MCP Server environment.

WHY IT NEEDS A POLICY

Why station.add_robot needs a policy

This tool creates a new robot entity within a RoboDK station, which is a write/create operation. It modifies the station state by adding a robot, but this is reversible (the robot can be removed). It does not execute code, delete data, or involve financial transactions. Severity is medium because misuse could corrupt a simulation setup or add unintended robots to a production workflow.

From the tool's definition "Add a robot to the current station" — creates/adds a new item to the simulation environment

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

station.add_robot Rate-limited

station.add_robot stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "station.add_robot": {
      "limits": [
        {
          "counter": "station.add_robot_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches RoboDK MCP Server, so you can run agents against it safely.

FAQ

Questions about station.add_robot

What does the station.add_robot tool do? +

Add a robot to the current station. It is categorised as a Write tool in the RoboDK MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on station.add_robot? +

Register the RoboDK MCP Server MCP server in PolicyLayer and add a rule for station.add_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 RoboDK MCP Server. Nothing to install.

What risk level is station.add_robot? +

station.add_robot is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit station.add_robot? +

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

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

station.add_robot is provided by the RoboDK MCP Server MCP server (lilyuppi/mcp_robodk). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.