AI agents invoke restore_named_view to trigger actions in GOLEM-3DMCP-Rhino-. 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.
Restoring a named view triggers an external operation in Rhino that changes the active viewport state (camera position, angle, zoom, etc.). It is not a pure read (it modifies the application state), not a write of persistent geometry, and not destructive. It executes a viewport/UI action within Rhino, making Execute the most appropriate category. Misuse could disorient the scene view but has limited blast radius.
From the tool's definition Restore a previously saved named view
Documented attack patterns abuse exactly the kind of access restore_named_view gives an agent:
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 restore_named_view:
{
"version": "1",
"default": "deny",
"tools": {
"restore_named_view": {
"limits": [
{
"counter": "restore_named_view_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}restore_named_view 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.
Restore a previously saved named view. It is categorised as a Execute tool in the GOLEM-3DMCP-Rhino- MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the GOLEM-3DMCP-Rhino- MCP server in PolicyLayer and add a rule for restore_named_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 GOLEM-3DMCP-Rhino-. Nothing to install.
restore_named_view 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 restore_named_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 restore_named_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.
restore_named_view 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.
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.