Set the camera position and orientation. Requires GUI mode. Args: position: Camera position as [x, y, z]. look_at: Point to look at as [x, y, z]. Uses origin if None. doc_name: Document to set camera for. Uses active document if None. Returns: Dictionary with result: - success: Whether operation ...
AI agents invoke set_camera_position to trigger actions in FreeCAD Robust MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Setting the camera position interacts with the FreeCAD GUI, triggering a visual state change in the application. It doesn't read, write persistent data, or destroy anything, but it does execute an action in an external application (FreeCAD's GUI). The blast radius is low since it only affects viewport orientation and is easily reversible.
From the tool's definition 'Set the camera position and orientation' and 'Requires GUI mode' — triggers an external operation in the FreeCAD GUI environment
Documented attack patterns abuse exactly the kind of access set_camera_position 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_camera_position:
{
"version": "1",
"default": "deny",
"tools": {
"set_camera_position": {
"limits": [
{
"counter": "set_camera_position_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}set_camera_position stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Set the camera position and orientation. Requires GUI mode. Args: position: Camera position as [x, y, z]. look_at: Point to look at as [x, y, z]. Uses origin if None. doc_name: Document to set camera for. Uses active document if None. Returns: Dictionary with result: - success: Whether operation was successful. It is categorised as a Execute tool in the FreeCAD Robust MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the FreeCAD Robust MCP Server MCP server in PolicyLayer and add a rule for set_camera_position: 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_camera_position is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the set_camera_position 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_camera_position. 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_camera_position 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.