Send a multi-line G-code program to the machine, one line at a time. Requires confirm=true.
AI agents invoke run_gcode_program to trigger actions in Cnc Fluidnc. 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.
This tool executes code (G-code programs) on a CNC router, triggering physical machinery operations. While the confirm=true requirement provides a safeguard, the tool's core function is to run arbitrary programs on external hardware with effects determined by user-supplied arguments.
From the tool's definition Tool description states 'Send a multi-line G-code program to the machine' - G-code programs control CNC router operations (cutting, drilling, movement) with irreversible physical consequences.
Attacks that exploit this kind of access
Send a multi-line G-code program to the machine, one line at a time. Requires confirm=true. It is categorised as a Execute tool in the Cnc Fluidnc MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Cnc Fluidnc MCP server in PolicyLayer and add a rule for run_gcode_program: 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 Cnc Fluidnc. Nothing to install.
run_gcode_program is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the run_gcode_program 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 run_gcode_program. 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.
run_gcode_program is provided by the Cnc Fluidnc MCP server (whitneydesignlabs/cnc-fluidnc-mcp). 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 →