Close a FreeCAD document. Args: doc_name: Name of document to close. Uses active document if None. save_changes: Whether to save changes before closing. Defaults to False. Returns: Dictionary with close result: - success: Whether close was successful - saved: Whether document was saved before clo...
AI agents use close_document 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.
Closing a document with save_changes=True performs a write operation that persists state to disk. Closing with save_changes=False discards unsaved changes. While not irreversible data deletion (Destructive) since the original file remains on disk unless explicitly deleted, this operation modifies application state and can cause loss of in-memory work.
From the tool's definition Tool description states it "Close[s] a FreeCAD document" with a parameter "save_changes: Whether to save changes before closing." The tool modifies document state by closing it and conditionally persists changes via the save_changes parameter.
Documented attack patterns abuse exactly the kind of access close_document 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 close_document:
{
"version": "1",
"default": "deny",
"tools": {
"close_document": {
"limits": [
{
"counter": "close_document_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}close_document 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.
Close a FreeCAD document. Args: doc_name: Name of document to close. Uses active document if None. save_changes: Whether to save changes before closing. Defaults to False. Returns: Dictionary with close result: - success: Whether close was successful - saved: Whether document was saved before closing. 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 close_document: 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.
close_document 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 close_document 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 close_document. 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.
close_document 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.