cfd_fluidx3d_results
AI agents call cfd_fluidx3d_results to retrieve information from FreeCAD MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The name pattern '*_results' strongly implies reading/fetching output data from a simulation. However, the description is empty, so confidence is reduced. Given the sibling tool 'cfd_build_case' exists separately, 'cfd_fluidx3d_results' likely retrieves already-computed results rather than triggering computation, placing it in the Read category.
From the tool's definition Tool name 'cfd_fluidx3d_results' suggests retrieval of CFD (Computational Fluid Dynamics) simulation results from FluidX3D; no description provided.
Attacks that exploit this kind of access
cfd_fluidx3d_results. It is categorised as a Read tool in the FreeCAD MCP MCP Server, which means it retrieves data without modifying state.
Register the FreeCAD MCP server in PolicyLayer and add a rule for cfd_fluidx3d_results: 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_results is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the cfd_fluidx3d_results 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_results. 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_results 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 →