convex_hull_3d
Compute the 3D convex hull of a point set, returning triangular faces.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/convex-hull-3d.md
What convex_hull_3d does on UnClick
AI agents invoke convex_hull_3d to trigger actions in UnClick. 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
points | array | Yes | Array of [x,y,z] points (at least 4) |
Parameters from the server's own tool schema.
Why convex_hull_3d is rated High
This tool runs a geometric computation (convex hull algorithm) on a provided point set and returns results. It doesn't read from a data store, write/modify persistent data, or perform destructive/financial operations. It executes a mathematical computation, placing it in the Execute category. Blast radius is low since it only processes input geometry with no side effects on external systems.
From the tool's definition 'Compute the 3D convex hull of a point set' — performs a computational algorithm on input data
Attacks that exploit this kind of access
The rule that runs convex_hull_3d safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For convex_hull_3d, this is the rule to start with:
convex_hull_3d 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.
The button opens the PolicyLayer dashboard: create your workspace, connect UnClick, apply this rule, and every convex_hull_3d call is checked against it from then on.
Questions about convex_hull_3d
Compute the 3D convex hull of a point set, returning triangular faces. It is categorised as a Execute tool in the UnClick MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
convex_hull_3d accepts 1 parameter: points. Required: points. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for convex_hull_3d: 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 UnClick. Nothing to install.
convex_hull_3d 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 convex_hull_3d 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 convex_hull_3d. 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.
convex_hull_3d is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
Across the catalogue