bezier_curve
Compute a Bezier curve from control points with arc length and optional evaluation.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/bezier-curve.md
What bezier_curve does on UnClick
AI agents invoke bezier_curve 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 |
|---|---|---|---|
steps | number | — | Number of curve samples (default 50, max 1000). |
eval_at | object | — | t value(s) in [0,1] to evaluate at. Number or array of numbers. |
control_points | array | Yes | Array of [x, y] control points (at least 2). |
Parameters from the server's own tool schema.
Why bezier_curve is rated High
The tool performs a mathematical computation (executing an algorithm) rather than simply reading stored data or writing/modifying data. It takes input control points, runs a curve computation, and returns derived results. No data is stored or destroyed; severity is low as misuse has minimal blast radius.
From the tool's definition Compute a Bezier curve from control points with arc length and optional evaluation
Attacks that exploit this kind of access
The rule that runs bezier_curve 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 bezier_curve, this is the rule to start with:
bezier_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.
The button opens the PolicyLayer dashboard: create your workspace, connect UnClick, apply this rule, and every bezier_curve call is checked against it from then on.
Questions about bezier_curve
Compute a Bezier curve from control points with arc length and optional evaluation. 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.
bezier_curve accepts 3 parameters: steps, eval_at, control_points. Required: control_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 bezier_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 UnClick. Nothing to install.
bezier_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 bezier_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 bezier_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.
bezier_curve 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