AI agents use create_object 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 creates new objects in FreeCAD documents, which is a reversible Write operation. While no description is given (lowering confidence slightly), the name and context within a CAD control suite clearly indicate object creation rather than deletion or execution. Severity is medium because creating unwanted objects in a CAD model could cause workflow disruption but is generally reversible via undo or deletion.
From the tool's definition Tool name 'create_object' indicates creation of new data within FreeCAD. Part of a suite that includes 'delete_object' and 'edit_object', placing it in the Write category. No description provided, reducing precision.
Documented attack patterns abuse exactly the kind of access create_object gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Freecad mcp, and nothing reaches the server without passing your rules. This is the rule we recommend for create_object:
{
"version": "1",
"default": "deny",
"tools": {
"create_object": {
"limits": [
{
"counter": "create_object_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_object 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_object. 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 create_object: 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.
create_object 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_object 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_object. 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_object is provided by the Freecad MCP server (neka-nat/freecad-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Freecad mcp, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
14 Freecad mcp tools catalogued and risk-classified — across an index of 43,000+ MCP servers.