robodk.start · RoboDK MCP Server MCP: Risk & Policy

WHAT IT DOES

What robodk.start does on RoboDK MCP Server

AI agents invoke robodk.start to trigger actions in RoboDK 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 robodk.start needs a policy

This tool starts an external application (RoboDK) or connects to a running instance. Launching external software constitutes triggering an external operation, which falls under Execute. Misuse could cause unintended robotics simulation software to run, but the blast radius is limited to the local system running RoboDK.

From the tool's definition Launch RoboDK or connect to existing instance

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

robodk.start Rate-limited

robodk.start 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": {
    "robodk.start": {
      "limits": [
        {
          "counter": "robodk.start_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 RoboDK MCP Server, so you can run agents against it safely.

FAQ

Questions about robodk.start

What does the robodk.start tool do? +

Launch RoboDK or connect to existing instance. It is categorised as a Execute tool in the RoboDK 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 robodk.start? +

Register the RoboDK MCP Server MCP server in PolicyLayer and add a rule for robodk.start: 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 robodk.start? +

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

Can I rate-limit robodk.start? +

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

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

robodk.start 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.