get_viewport_screenshot

Capture a screenshot of the current Blender 3D viewport.

SERVERAos SOURCE@hybridlabor-api/aos

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/hybridlabor-api-aos/get-viewport-screenshot.md

WHAT IT DOES

What get_viewport_screenshot does on Aos

AI agents call get_viewport_screenshot 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.

RISK

Why get_viewport_screenshot is rated Low

The tool captures and returns an image of the current viewport state. This is a read-only operation with no side effects, no data modification, and no external execution. It merely observes and returns the current visual state of Blender's 3D viewport.

From the tool's definition Tool name and description: 'Capture a screenshot of the current Blender 3D viewport.' This retrieves visual data from the viewport without modifying any state, creating assets, or triggering external operations.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_viewport_screenshot 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 get_viewport_screenshot, this is the rule to start with:

get_viewport_screenshot Allowed

get_viewport_screenshot is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_viewport_screenshot": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Aos, apply this rule, and every get_viewport_screenshot call is checked against it from then on.

FAQ

Questions about get_viewport_screenshot

What does the get_viewport_screenshot tool do? +

Capture a screenshot of the current Blender 3D viewport. It is categorised as a Read tool in the Aos MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_viewport_screenshot? +

Register the Aos MCP server in PolicyLayer and add a rule for get_viewport_screenshot: 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.

What risk level is get_viewport_screenshot? +

get_viewport_screenshot is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_viewport_screenshot? +

Yes. Add a rate_limit block to the get_viewport_screenshot 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.

How do I block get_viewport_screenshot completely? +

Set action: deny in the PolicyLayer policy for get_viewport_screenshot. 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.

What MCP server provides get_viewport_screenshot? +

get_viewport_screenshot 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.

KEEP EXPLORING

More on Aos, and thousands of servers like it.

This server

All 719 Aos tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_file_snippet on ACE-MCP →get_torrent_detail on M-Team MCP Server →get_customer_data on 08-AI-Business-Agent → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →