AI agents invoke new_document 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.
Creating a new document in Rhino 8 is an Execute-category action because it triggers state changes and operations in an external application whose effects depend on the current Rhino context and subsequent commands.
From the tool's definition Tool is part of GOLEM-3DMCP server that 'give[s] AI agents direct, programmatic control of Rhino 8' and enables actions like 'create geometry, run booleans, drive Grasshopper, capture viewports, and execute arbitrary Python scripts'.
Documented attack patterns abuse exactly the kind of access new_document 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 new_document:
{
"version": "1",
"default": "deny",
"tools": {
"new_document": {
"limits": [
{
"counter": "new_document_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}new_document 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.
new_document. 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 new_document: 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.
new_document 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 new_document 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 new_document. 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.
new_document 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.