Execute arbitrary Python code in FreeCAD.
AI agents invoke execute_code 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 permits execution of arbitrary Python code, which is the definition of the Execute category. The blast radius is critical because: (1) Python code execution in FreeCAD can access the file system, modify application state, trigger external processes, and access network resources; (2) an AI agent with unrestricted code execution could instantiate destructive operations (delete files, overwrite documents) or…
From the tool's definition Tool name is 'execute_code' with description 'Execute arbitrary Python code in FreeCAD.' The word 'arbitrary' combined with 'Execute' and 'Python code' directly indicates the ability to run unrestricted code within the FreeCAD environment.
Attacks that exploit this kind of access
Execute arbitrary Python code in FreeCAD. 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 execute_code: 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.
execute_code 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 execute_code 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 execute_code. 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.
execute_code is provided by the FreeCAD MCP server (yaeshio/freecad-mcp-for-ydga). 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 →