Create a new empty station or open an existing one.
AI agents use robodk.open_station 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.
This tool creates or modifies application state by either instantiating new stations or switching active contexts. While not as severe as Execute (which might run arbitrary commands) or Destructive (which would permanently delete data), it is a Write operation that reversibly changes the RoboDK environment.
From the tool's definition Tool description states it can 'Create a new empty station or open an existing one.' Creating a new station modifies the state of the RoboDK application by adding a new project entity.
Attacks that exploit this kind of access
Create a new empty station or open an existing one. 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.
Register the RoboDK MCP Server MCP server in PolicyLayer and add a rule for robodk.open_station: 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.
robodk.open_station is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the robodk.open_station 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.
Set action: deny in the PolicyLayer policy for robodk.open_station. 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.
robodk.open_station 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →