Create a custom polyhedron from vertices and faces
AI agents use create_polyhedron to create or update resources in 3D MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your 3D MCP Server environment.
This tool creates new geometric objects (polyhedra) in the 3D model space. It is a Write operation because it creates or modifies data reversibly—polyhedra can be deleted or modified afterwards using sibling tools like 'remove_object' or 'custom_scad'. It does not execute arbitrary code (Execute), destroy data (Destructive), or move money (Financial).
From the tool's definition Tool creates custom polyhedron from vertices and faces, adding new 3D model data. Description indicates data creation without deletion or irreversible modification.
Attacks that exploit this kind of access
Create a custom polyhedron from vertices and faces. It is categorised as a Write tool in the 3D MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the 3D MCP Server MCP server in PolicyLayer and add a rule for create_polyhedron: 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 3D MCP Server. Nothing to install.
create_polyhedron 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 create_polyhedron 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 create_polyhedron. 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.
create_polyhedron is provided by the 3D MCP Server MCP server (jagjerez-org/3d-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →