segment_intersection
Find all pairwise intersections among a set of 2D line segments, returning intersection points.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/segment-intersection.md
What segment_intersection does on UnClick
AI agents use segment_intersection to create or update resources in UnClick, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your UnClick environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
segments | array | Yes | Array of line segments (max 1000) |
Parameters from the server's own tool schema.
Why segment_intersection is rated Medium
An AI agent can call segment_intersection faster than any human can review: one bad instruction and it creates or modifies resources in UnClick by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs segment_intersection 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 segment_intersection, this is the rule to start with:
segment_intersection 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.
The button opens the PolicyLayer dashboard: create your workspace, connect UnClick, apply this rule, and every segment_intersection call is checked against it from then on.
Questions about segment_intersection
Find all pairwise intersections among a set of 2D line segments, returning intersection points. It is categorised as a Write tool in the UnClick MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
segment_intersection accepts 1 parameter: segments. Required: segments. 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 segment_intersection: 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.
segment_intersection 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 segment_intersection 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 segment_intersection. 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.
segment_intersection 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