AI agents invoke sweep_2_rails 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.
The tool name 'sweep_2_rails' strongly suggests a Rhino 3D modeling operation (two-rail sweep) that creates geometry by sweeping a profile along two rail curves. This is a geometry creation/modification operation. The description is empty, lowering confidence. Based on the server context and naming convention, this likely executes a Rhino command to generate 3D geometry.
From the tool's definition Tool name 'sweep_2_rails' on a server that provides 'direct, programmatic control of Rhino 8' to 'create geometry, run booleans, drive Grasshopper, capture viewports, and execute arbitrary Python scripts'.
Documented attack patterns abuse exactly the kind of access sweep_2_rails 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 sweep_2_rails:
{
"version": "1",
"default": "deny",
"tools": {
"sweep_2_rails": {
"limits": [
{
"counter": "sweep_2_rails_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}sweep_2_rails 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.
sweep_2_rails. 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 sweep_2_rails: 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.
sweep_2_rails 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 sweep_2_rails 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 sweep_2_rails. 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.
sweep_2_rails 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.