counting_sort
Sort an array of integers in O(n+k) time using counting sort, with frequency analysis.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/counting-sort.md
What counting_sort does on UnClick
AI agents call counting_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 |
|---|---|---|---|
values | array | Yes | Array of integers to sort |
Parameters from the server's own tool schema.
Why counting_sort is rated Low
Counting sort is a deterministic algorithm that processes input data to produce a sorted output. It does not create, modify, delete, or execute external operations. The frequency analysis component is likewise analytical. No side effects occur beyond computing and returning results. This is a pure computational utility, not a data-mutating or destructive operation.
From the tool's definition Tool performs sorting and frequency analysis on provided data. Description states 'Sort an array of integers' and 'frequency analysis'—both read-only operations that examine data without modification, deletion, or execution of arbitrary code.
Attacks that exploit this kind of access
The rule that runs counting_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 counting_sort, this is the rule to start with:
counting_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 counting_sort call is checked against it from then on.
Questions about counting_sort
Sort an array of integers in O(n+k) time using counting sort, with frequency analysis. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
counting_sort accepts 1 parameter: values. Required: values. 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 counting_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.
counting_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 counting_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 counting_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.
counting_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