Create a new FreeCAD macro. The macro will be created in the user's macro directory with standard FreeCAD imports automatically added. Args: name: Macro name (without .FCMacro extension). code: Python code for the macro body. description: Optional description for the macro. Returns: Dictionary wi...
AI agents use create_macro to create or update resources in FreeCAD Robust MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your FreeCAD Robust MCP Server environment.
This tool creates and stores new data (macro files) in the filesystem, which is reversible—the created macro can be edited, renamed, or deleted later. It does not execute the macro or trigger external operations automatically. While the macro *contains* arbitrary Python code that could later be executed, the create_macro tool itself only performs the write operation of file creation.
From the tool's definition Tool creates a new FreeCAD macro file in the user's macro directory. Description explicitly states 'Create a new FreeCAD macro' and accepts name, code, and description parameters to generate and store a new macro file.
Documented attack patterns abuse exactly the kind of access create_macro gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and FreeCAD Robust MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for create_macro:
{
"version": "1",
"default": "deny",
"tools": {
"create_macro": {
"limits": [
{
"counter": "create_macro_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_macro stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Create a new FreeCAD macro. The macro will be created in the user's macro directory with standard FreeCAD imports automatically added. Args: name: Macro name (without .FCMacro extension). code: Python code for the macro body. description: Optional description for the macro. Returns: Dictionary with created macro information: - name: Macro name - path: Full path to created macro file - description: Macro description. It is categorised as a Write tool in the FreeCAD Robust MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the FreeCAD Robust MCP Server MCP server in PolicyLayer and add a rule for create_macro: 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 Robust MCP Server. Nothing to install.
create_macro 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 create_macro 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 create_macro. 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.
create_macro is provided by the FreeCAD Robust MCP Server MCP server (spkane/freecad-addon-robust-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 152 FreeCAD Robust MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
152 FreeCAD Robust MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.