High Risk →

reload_handlers

Hot-reload all FreeCAD addon handler modules.

How to control reload_handlers ↓

What reload_handlers does on FreeCAD MCP Server

AI agents invoke reload_handlers to trigger actions in FreeCAD 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.

High Risk

Why reload_handlers needs a policy

Hot-reloading handler modules executes code loading operations that replace live modules in the running FreeCAD instance. This is an Execute-level action because it triggers external operations (module reloading) whose effects depend on the current state of the addon code.

From the tool's definition Hot-reload all FreeCAD addon handler modules

Documented attack patterns abuse exactly the kind of access reload_handlers gives an agent:

How to control reload_handlers

PolicyLayer is an MCP gateway — it sits between your AI agents and FreeCAD MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for reload_handlers:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "reload_handlers": {
      "limits": [
        {
          "counter": "reload_handlers_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

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

  1. Create a free account and register FreeCAD MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RATE-LIMIT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about reload_handlers

What does the reload_handlers tool do? +

Hot-reload all FreeCAD addon handler modules. It is categorised as a Execute tool in the FreeCAD 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 reload_handlers? +

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

What risk level is reload_handlers? +

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

Can I rate-limit reload_handlers? +

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

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

reload_handlers is provided by the FreeCAD MCP Server MCP server (theosib/freecad-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every FreeCAD MCP Server tool call.

Start from FreeCAD MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

9 FreeCAD MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.