Save the current camera position of a viewport as a named view.
AI agents use add_named_view to create or update resources in GOLEM-3DMCP-Rhino- — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your GOLEM-3DMCP-Rhino- environment.
This tool creates or stores a new named view configuration (camera position) within the Rhino document. It is a reversible Write operation—the named view can be deleted or overwritten later. It does not execute arbitrary code, destroy data, or cause financial impact. The blast radius of misuse is limited to unwanted viewport configurations being stored, which is easily correctable.
From the tool's definition Tool description: 'Save the current camera position of a viewport as a named view.' The verb 'Save' and the action of persisting camera state as a named view constitute data creation/modification.
Documented attack patterns abuse exactly the kind of access add_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 add_named_view:
{
"version": "1",
"default": "deny",
"tools": {
"add_named_view": {
"limits": [
{
"counter": "add_named_view_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}add_named_view stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Save the current camera position of a viewport as a named view. It is categorised as a Write tool in the GOLEM-3DMCP-Rhino- MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the GOLEM-3DMCP-Rhino- MCP server in PolicyLayer and add a rule for add_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.
add_named_view is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the add_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 add_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.
add_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.