Move an object to a new absolute position. Specify at least one coordinate.
AI agents use freecad_move_object 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 modifies the position of an existing object in FreeCAD by updating its coordinates. It's a reversible modification (the object can be moved back), so it falls under Write rather than Destructive. Misuse could displace design elements in a CAD model, potentially corrupting designs if positions are set incorrectly.
From the tool's definition Move an object to a new absolute position. Specify at least one coordinate.
Documented attack patterns abuse exactly the kind of access freecad_move_object 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 freecad_move_object:
{
"version": "1",
"default": "deny",
"tools": {
"freecad_move_object": {
"limits": [
{
"counter": "freecad_move_object_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} freecad_move_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.
Move an object to a new absolute position. Specify at least one coordinate. 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 freecad_move_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 Mcp Freecad. Nothing to install.
freecad_move_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 freecad_move_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 freecad_move_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.
freecad_move_object 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.