treap_sim
Simulate a treap (randomized BST): insert values, get sorted output, tree height, and search.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/treap-sim.md
What treap_sim does on UnClick
AI agents invoke treap_sim 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 |
|---|---|---|---|
search | array | — | Values to search for |
values | array | Yes | Values to insert |
Parameters from the server's own tool schema.
Why treap_sim is rated High
The tool runs a simulation of a data structure (treap), executing computational operations like insertions and searches. It doesn't read external data, write to persistent storage, or perform destructive/financial actions. It qualifies as Execute due to running an algorithmic simulation, with low severity since it's a self-contained computation with no external side effects.
From the tool's definition 'Simulate a treap (randomized BST): insert values, get sorted output, tree height, and search'
Attacks that exploit this kind of access
The rule that runs treap_sim 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 treap_sim, this is the rule to start with:
treap_sim 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 treap_sim call is checked against it from then on.
Questions about treap_sim
Simulate a treap (randomized BST): insert values, get sorted output, tree height, and search. 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.
treap_sim accepts 2 parameters: search, 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 treap_sim: 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.
treap_sim 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 treap_sim 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 treap_sim. 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.
treap_sim 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