AI agents use create_cone to create or update resources in Mcp Freecad — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Freecad environment.
This tool creates a new geometric object in FreeCAD, which is a reversible write operation. The user can delete the cone or undo the action. It does not execute arbitrary code, delete data irreversibly, or involve financial transactions. Severity is medium because misuse by an AI could clutter or corrupt a CAD document, but the effects are easily undone through standard CAD operations.
From the tool's definition Tool name 'create_cone' and description 'Create a cone primitive in FreeCAD' indicate object creation within a CAD document.
Documented attack patterns abuse exactly the kind of access create_cone gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Freecad, and nothing reaches the server without passing your rules. This is the rule we recommend for create_cone:
{
"version": "1",
"default": "deny",
"tools": {
"create_cone": {
"limits": [
{
"counter": "create_cone_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_cone 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 cone primitive in FreeCAD. It is categorised as a Write tool in the Mcp Freecad MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Freecad MCP server in PolicyLayer and add a rule for create_cone: 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 Mcp Freecad. Nothing to install.
create_cone 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_cone 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_cone. 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_cone is provided by the Mcp Freecad MCP server (jango-blockchained/mcp-freecad). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Mcp Freecad, 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.
34 Mcp Freecad tools catalogued and risk-classified — across an index of 43,000+ MCP servers.