AI agents use mesh_from_surface 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.
The tool creates a new mesh representation from a surface, which is a reversible data creation/modification operation (Write category). It does not delete or overwrite existing data (not Destructive), does not execute arbitrary code (not Execute), and has no financial impact.
From the tool's definition Tool name 'mesh_from_surface' indicates creation of a new mesh object from existing geometry. The server description emphasizes 'create geometry' as a primary capability, and this tool fits that pattern of creating/modifying CAD objects.
Documented attack patterns abuse exactly the kind of access mesh_from_surface 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 mesh_from_surface:
{
"version": "1",
"default": "deny",
"tools": {
"mesh_from_surface": {
"limits": [
{
"counter": "mesh_from_surface_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}mesh_from_surface 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.
mesh_from_surface. 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 mesh_from_surface: 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.
mesh_from_surface 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 mesh_from_surface 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 mesh_from_surface. 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.
mesh_from_surface 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.