get_view
AI agents call get_view to retrieve information from FreeCAD MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'get' prefix is a strong indicator of read-only retrieval operations. Even without description, getting a view in CAD software typically means querying the current viewport state, camera position, or visual configuration—all non-destructive reads. The broader server context (capturing screenshots, managing objects) confirms read semantics.
From the tool's definition Tool name 'get_view' suggests retrieval of view data or state. No description provided, but naming convention and context within FreeCAD (a 3D modeling tool) indicate this retrieves workspace/viewport information without modification.
Attacks that exploit this kind of access
get_view. It is categorised as a Read tool in the FreeCAD MCP MCP Server, which means it retrieves data without modifying state.
Register the FreeCAD MCP server in PolicyLayer and add a rule for get_view: 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 MCP. Nothing to install.
get_view is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_view 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 get_view. 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.
get_view is provided by the FreeCAD MCP server (lzy-hhhh/freecad). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →