AI agents invoke extrude_curve 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.
Based on the server context and sibling tools, extrude_curve likely creates 3D geometry by extruding a curve in Rhino. This is a geometry creation/modification operation (Write/Execute). Given the server's capability to execute arbitrary Python scripts and drive Grasshopper, and that extrusion triggers an operation in an external application (Rhino), it fits Execute. The description is empty, lowering confidence.
From the tool's definition Tool name 'extrude_curve' on a server that 'create geometry, run booleans, drive Grasshopper... execute arbitrary Python scripts' — sibling tools perform geometric operations (boolean_difference, boolean_union, cap_planar_holes, array_objects_linear)
Documented attack patterns abuse exactly the kind of access extrude_curve 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 extrude_curve:
{
"version": "1",
"default": "deny",
"tools": {
"extrude_curve": {
"limits": [
{
"counter": "extrude_curve_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} extrude_curve 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.
extrude_curve. 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 extrude_curve: 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.
extrude_curve 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 extrude_curve 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 extrude_curve. 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.
extrude_curve 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.