AI agents invoke execute_rhinoscript 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.
This tool executes arbitrary scripts in the Rhino environment, giving an AI agent the ability to run code whose effects depend entirely on script content. While the tool description is empty, the name and server context make the Execute category clear. Severity is high rather than critical because the blast radius is limited to Rhino's local geometry operations, not system-level or financial impacts.
From the tool's definition Tool name is 'execute_rhinoscript' which explicitly indicates execution of RhinoScript code. Server description states the system gives 'AI agents direct, programmatic control of Rhino 8' and mentions 'execute arbitrary Python scripts' as a core capability.
Documented attack patterns abuse exactly the kind of access execute_rhinoscript 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 execute_rhinoscript:
{
"version": "1",
"default": "deny",
"tools": {
"execute_rhinoscript": {
"limits": [
{
"counter": "execute_rhinoscript_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}execute_rhinoscript 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.
execute_rhinoscript. 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 execute_rhinoscript: 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.
execute_rhinoscript 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 execute_rhinoscript 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 execute_rhinoscript. 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.
execute_rhinoscript 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.