cfd_nl2foam
AI agents invoke cfd_nl2foam 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.
Based on the server context (fluid simulation capabilities) and the tool name pattern 'nl2foam' (natural language to OpenFOAM), this tool likely executes CFD simulation setup or conversion operations. Given sibling tool 'cfd_build_case', this probably generates or executes OpenFOAM configuration from natural language input. Empty description lowers confidence significantly.
From the tool's definition Tool name 'cfd_nl2foam' suggests CFD (Computational Fluid Dynamics) operations, likely converting natural language descriptions to OpenFOAM simulation cases. Description is empty and uninformative.
Attacks that exploit this kind of access
cfd_nl2foam. 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_nl2foam: 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_nl2foam 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_nl2foam 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_nl2foam. 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_nl2foam 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 →