Low Risk

capture_viewport

capture_viewport

How to control capture_viewport ↓

What capture_viewport does on GOLEM-3DMCP-Rhino-

AI agents call capture_viewport to retrieve information from GOLEM-3DMCP-Rhino- without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why capture_viewport needs a policy

Based on the name and server description mentioning viewport capture, this tool likely takes a screenshot or image of the current Rhino viewport — a read/query operation with no side effects. Confidence is reduced due to the empty description. Severity is medium because viewport captures could expose sensitive design data if misused.

From the tool's definition Tool name 'capture_viewport' and server context mentioning 'capture viewports' as a feature. Description is empty.

Documented attack patterns abuse exactly the kind of access capture_viewport gives an agent:

How to control capture_viewport

PolicyLayer is an MCP gateway — it sits between your AI agents and GOLEM-3DMCP-Rhino-, and nothing reaches the server without passing your rules. This is the rule we recommend for capture_viewport:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "capture_viewport": {}
  }
}

capture_viewport is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register GOLEM-3DMCP-Rhino- — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about capture_viewport

What does the capture_viewport tool do? +

capture_viewport. It is categorised as a Read tool in the GOLEM-3DMCP-Rhino- MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on capture_viewport? +

Register the GOLEM-3DMCP-Rhino- 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 GOLEM-3DMCP-Rhino-. Nothing to install.

What risk level is capture_viewport? +

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

Can I rate-limit capture_viewport? +

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.

How do I block capture_viewport completely? +

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.

What MCP server provides capture_viewport? +

capture_viewport is provided by the GOLEM-3DMCP-Rhino- MCP server (thekinghippopotamus/golem-3dmcp-rhino-). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every GOLEM-3DMCP-Rhino- tool call.

Start from GOLEM-3DMCP-Rhino-, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

89 GOLEM-3DMCP-Rhino- tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.