bezier_clip
Extract a Bezier sub-curve for a parameter range using de Casteljau subdivision.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/bezier-clip.md
What bezier_clip does on UnClick
AI agents call bezier_clip to retrieve information from UnClick without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
t_end | number | Yes | End parameter (0-1) |
t_start | number | Yes | Start parameter (0-1) |
control_points | array | Yes | Array of [x,y] control points |
Parameters from the server's own tool schema.
Why bezier_clip is rated Low
This is a pure computational geometry function. It takes a Bezier curve and a parameter range as inputs and returns a sub-curve segment. No data is created, modified, deleted, or persisted. No external operations are triggered. The operation is read-like in that it queries/derives information from input parameters without side effects.
From the tool's definition Tool 'extracts' a Bezier sub-curve using de Casteljau subdivision algorithm. The description indicates a mathematical operation that retrieves/computes a geometric segment without modifying any persistent state or executing external commands.
Attacks that exploit this kind of access
The rule that runs bezier_clip 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_clip, this is the rule to start with:
bezier_clip is read-only, so it stays allowed. 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_clip call is checked against it from then on.
Questions about bezier_clip
Extract a Bezier sub-curve for a parameter range using de Casteljau subdivision. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
bezier_clip accepts 3 parameters: t_end, t_start, control_points. Required: t_end, t_start, 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_clip: 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_clip is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the bezier_clip 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_clip. 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_clip 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.
This server
Across the catalogue