Set the visibility of a FreeCAD object. Args: object_name: Name of the object. visible: Whether object should be visible. doc_name: Document containing the object. Uses active document if None. Returns: Dictionary with result: - success: Whether operation was successful - visible: New visibility ...
AI agents use set_object_visibility 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 modifies object metadata (visibility flag) in a FreeCAD document but does not create, delete, or execute arbitrary operations. The change is fully reversible—visibility can be toggled on and off without data loss or side effects. While it affects the visual representation, it does not alter geometry, execute code, or destroy data.
From the tool's definition Tool sets the visibility state of a FreeCAD object via the 'visible' parameter, modifying object properties. The description explicitly states it 'Set the visibility of a FreeCAD object', which is a reversible state change.
Documented attack patterns abuse exactly the kind of access set_object_visibility 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 set_object_visibility:
{
"version": "1",
"default": "deny",
"tools": {
"set_object_visibility": {
"limits": [
{
"counter": "set_object_visibility_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}set_object_visibility 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.
Set the visibility of a FreeCAD object. Args: object_name: Name of the object. visible: Whether object should be visible. doc_name: Document containing the object. Uses active document if None. Returns: Dictionary with result: - success: Whether operation was successful - visible: New visibility state. 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 set_object_visibility: 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.
set_object_visibility 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 set_object_visibility 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 set_object_visibility. 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.
set_object_visibility 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.