bucket_sort
Sort numbers using the bucket sort algorithm. Distributes elements into buckets, sorts each, then concatenates.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/bucket-sort.md
What bucket_sort does on UnClick
AI agents call bucket_sort 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 |
|---|---|---|---|
array | array | Yes | Array of numbers to sort |
bucket_count | number | — | Number of buckets (default: sqrt of array length) |
Parameters from the server's own tool schema.
Why bucket_sort is rated Low
The bucket_sort tool is a stateless sorting utility that takes numbers as input and returns a sorted result. It does not create, modify, delete, or execute anything—it merely computes and returns data. This is a read-only computational operation with minimal security risk.
From the tool's definition Tool performs 'Sort numbers using the bucket sort algorithm. Distributes elements into buckets, sorts each, then concatenates.' This is a pure computational algorithm with no side effects, no data modification, no execution of external commands, and no…
Attacks that exploit this kind of access
The rule that runs bucket_sort 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 bucket_sort, this is the rule to start with:
bucket_sort 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 bucket_sort call is checked against it from then on.
Questions about bucket_sort
Sort numbers using the bucket sort algorithm. Distributes elements into buckets, sorts each, then concatenates. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
bucket_sort accepts 2 parameters: array, bucket_count. Required: array. 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 bucket_sort: 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.
bucket_sort 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 bucket_sort 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 bucket_sort. 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.
bucket_sort 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