euler_tour
Compute Euler tour of a tree with tin/tout timestamps, depths, and subtree sizes.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/euler-tour.md
What euler_tour does on UnClick
AI agents invoke euler_tour 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 |
|---|---|---|---|
root | number | — | Root vertex (default 0) |
edges | array | Yes | Tree edges as [u, v] pairs (0-indexed) |
vertex_count | number | Yes | Number of vertices |
Parameters from the server's own tool schema.
Why euler_tour is rated High
This tool performs a computational algorithm (Euler tour traversal) on a tree data structure, producing derived values like timestamps, depths, and subtree sizes. It executes a computation rather than simply reading stored data or writing/modifying persistent data. There are no destructive, financial, or write side effects apparent.
From the tool's definition 'Compute Euler tour of a tree with tin/tout timestamps, depths, and subtree sizes'
Attacks that exploit this kind of access
The rule that runs euler_tour 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 euler_tour, this is the rule to start with:
euler_tour 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 euler_tour call is checked against it from then on.
Questions about euler_tour
Compute Euler tour of a tree with tin/tout timestamps, depths, and subtree sizes. 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.
euler_tour accepts 3 parameters: root, edges, vertex_count. Required: edges, vertex_count. 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 euler_tour: 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.
euler_tour 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 euler_tour 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 euler_tour. 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.
euler_tour 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