kmeans_cluster
Partition points into k clusters using the k-means algorithm.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/kmeans-cluster.md
What kmeans_cluster does on UnClick
AI agents invoke kmeans_cluster 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 |
|---|---|---|---|
k | number | — | Number of clusters (default 3) |
points | array | Yes | Array of numeric vectors (all same dimension) |
max_iterations | number | — | Max iterations (default 100) |
Parameters from the server's own tool schema.
Why kmeans_cluster is rated High
This tool executes a k-means clustering algorithm on provided data points. It performs computation rather than simply reading stored data or writing/modifying persistent state. The blast radius is low since it only performs an in-memory calculation and returns cluster assignments without storing results or affecting external systems.
From the tool's definition 'Partition points into k clusters using the k-means algorithm' — runs a computational algorithm on input data
Attacks that exploit this kind of access
The rule that runs kmeans_cluster 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 kmeans_cluster, this is the rule to start with:
kmeans_cluster 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 kmeans_cluster call is checked against it from then on.
Questions about kmeans_cluster
Partition points into k clusters using the k-means algorithm. 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.
kmeans_cluster accepts 3 parameters: k, points, max_iterations. 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 kmeans_cluster: 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.
kmeans_cluster 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 kmeans_cluster 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 kmeans_cluster. 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.
kmeans_cluster 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