shell_sort
Sort an array using Shell sort with gap sequence tracking, comparison and swap counts.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/shell-sort.md
What shell_sort does on UnClick
AI agents invoke shell_sort 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 |
|---|---|---|---|
array | array | Yes | Array of numbers to sort (max 100,000 elements) |
Parameters from the server's own tool schema.
Why shell_sort is rated High
This tool appears to perform an in-memory sorting algorithm (Shell sort) on a provided array. It does not read external data, write to storage, delete anything, or handle finances. The 'Execute' category fits because it runs a computational algorithm/operation rather than simply retrieving data. Severity is low since it only processes input data in memory with no apparent side effects on external systems.
From the tool's definition 'Sort an array using Shell sort with gap sequence tracking, comparison and swap counts'
Attacks that exploit this kind of access
The rule that runs shell_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 shell_sort, this is the rule to start with:
shell_sort 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 shell_sort call is checked against it from then on.
Questions about shell_sort
Sort an array using Shell sort with gap sequence tracking, comparison and swap counts. 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.
shell_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 shell_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.
shell_sort 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 shell_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 shell_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.
shell_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.
Across the catalogue