cfd_fluidx3d_export_for_render
AI agents use cfd_fluidx3d_export_for_render to create or update resources in FreeCAD MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your FreeCAD MCP environment.
The tool exports CFD (computational fluid dynamics) simulation results, which creates new output files or data structures. This is a Write operation—it generates and persists data (export artefacts) but doesn't delete, execute arbitrary code, or cause financial impact.
From the tool's definition Tool name 'cfd_fluidx3d_export_for_render' indicates exporting fluid simulation data; the 'export' operation creates or writes output files/data. Description is empty, limiting certainty.
Attacks that exploit this kind of access
cfd_fluidx3d_export_for_render. It is categorised as a Write tool in the FreeCAD MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the FreeCAD MCP server in PolicyLayer and add a rule for cfd_fluidx3d_export_for_render: 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_export_for_render is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the cfd_fluidx3d_export_for_render 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_export_for_render. 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_export_for_render 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 →