heap_sort
Sort numbers using the heap sort algorithm. Guaranteed O(n log n) in-place sorting with swap count.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/heap-sort.md
What heap_sort does on UnClick
AI agents call heap_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 |
Parameters from the server's own tool schema.
Why heap_sort is rated Low
Heap sort is a deterministic, in-place sorting algorithm that reads input data and returns transformed output. No data is created, deleted, modified in storage, or destroyed. No external systems are invoked. No financial transactions occur. This is a Read category tool because it retrieves/computes and returns information without irreversible side effects.
From the tool's definition Tool performs 'Sort numbers using the heap sort algorithm' — a pure computational operation with no side effects, no data modification, no external state changes, and no command execution. It returns sorted data and swap count metadata.
Attacks that exploit this kind of access
The rule that runs heap_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 heap_sort, this is the rule to start with:
heap_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 heap_sort call is checked against it from then on.
Questions about heap_sort
Sort numbers using the heap sort algorithm. Guaranteed O(n log n) in-place sorting with swap count. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
heap_sort accepts 1 parameter: array. 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 heap_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.
heap_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 heap_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 heap_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.
heap_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