home_axes · Cnc Fluidnc MCP: Risk & Policy

WHAT IT DOES

What home_axes does on Cnc Fluidnc

AI agents invoke home_axes 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.

WHY IT NEEDS A POLICY

Why home_axes needs a policy

This tool executes hardware operations on a CNC machine—homing axes is an active command that moves mechanical components. While not destructive or financial, it performs a real-world action that could cause physical damage if misused (e.g., if axes are misaligned or obstructed). This fits Execute rather than Read or Write because it runs an external operation (CNC firmware command) with physical consequences.

From the tool's definition 'Run homing cycle' is a machine control operation that executes a specific firmware command on CNC hardware. The tool triggers physical movement of machine axes, which is an external operation whose effects depend on arguments (which axes to home).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

home_axes Rate-limited

home_axes 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": {
    "home_axes": {
      "limits": [
        {
          "counter": "home_axes_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 Cnc Fluidnc, so you can run agents against it safely.

FAQ

Questions about home_axes

What does the home_axes tool do? +

Run homing cycle. Homes all axes by default, or specify individual axes. 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.

How do I enforce a policy on home_axes? +

Register the Cnc Fluidnc MCP server in PolicyLayer and add a rule for home_axes: 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.

What risk level is home_axes? +

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

Can I rate-limit home_axes? +

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

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

home_axes 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.