cfd_fluidx3d_run
AI agents invoke cfd_fluidx3d_run to trigger actions in FreeCAD MCP. 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 external computational operations (fluid dynamics simulation) whose effects depend on simulation parameters and case configuration. Simulation execution is irreversible in terms of time/resources consumed and could produce arbitrary results based on input. While not destructive to persistent data or financial in nature, it triggers complex external operations, placing it in Execute category.
From the tool's definition Tool name 'cfd_fluidx3d_run' indicates execution of a fluid dynamics simulation (FluidX3D). The description is empty, but context from sibling tools (cfd_build_case) and server description ('fluid simulation') confirm this runs computational simulations.
Attacks that exploit this kind of access
cfd_fluidx3d_run. It is categorised as a Execute tool in the FreeCAD MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the FreeCAD MCP server in PolicyLayer and add a rule for cfd_fluidx3d_run: 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. Nothing to install.
cfd_fluidx3d_run 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 cfd_fluidx3d_run 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 cfd_fluidx3d_run. 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.
cfd_fluidx3d_run is provided by the FreeCAD MCP server (sandraschi/freecad-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 →