This record as markdown: /tools/hybridlabor-api-aos/capture-viewport.md
What capture_viewport does on Aos
AI agents call capture_viewport to retrieve information from Aos without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why capture_viewport is rated Low
Capturing a viewport is a non-destructive retrieval operation with no side effects on the underlying model or data. It acquires visual information (a snapshot of the current view) without modifying, executing external operations, or creating persistent changes. Consistent with the server's read-only designation.
From the tool's definition Server is explicitly described as 'Read-only Fusion 360 MCP'. Tool name 'capture_viewport' suggests acquiring/retrieving a screenshot or view state rather than modifying data.
Attacks that exploit this kind of access
The rule that runs capture_viewport safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Aos, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For capture_viewport, this is the rule to start with:
capture_viewport is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Aos, apply this rule, and every capture_viewport call is checked against it from then on.
Questions about capture_viewport
capture_viewport is a read tool on the Aos MCP server. It is categorised as a Read tool in the Aos MCP Server, which means it retrieves data without modifying state.
Register the Aos MCP server in PolicyLayer and add a rule for capture_viewport: 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 Aos. Nothing to install.
capture_viewport 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 capture_viewport 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 capture_viewport. 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.
capture_viewport is provided by the Aos MCP server (@hybridlabor-api/aos). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Aos, and thousands of servers like it.
This server
Across the catalogue