topo_count
Count the number of distinct topological orderings of a DAG.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/topo-count.md
What topo_count does on UnClick
AI agents call topo_count 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 |
|---|---|---|---|
edges | array | Yes | Directed edges as [from, to] pairs |
num_nodes | number | Yes | Number of nodes (max 20) |
Parameters from the server's own tool schema.
Why topo_count is rated Low
This is a pure mathematical computation tool. It takes a directed acyclic graph (DAG) as input and computes a derived value (count of topological orderings) without mutating state, executing external commands, or affecting external systems. The misuse risk is minimal—an agent could only waste computational resources or receive incorrect mathematical results.
From the tool's definition Tool 'topo_count' performs a computational query to 'count the number of distinct topological orderings of a DAG.' The description indicates read-only behavior: it retrieves/calculates a count without modifying any underlying data, creating side effects,…
Attacks that exploit this kind of access
The rule that runs topo_count 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 topo_count, this is the rule to start with:
topo_count 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 topo_count call is checked against it from then on.
Questions about topo_count
Count the number of distinct topological orderings of a DAG. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
topo_count accepts 2 parameters: edges, num_nodes. Required: edges, num_nodes. 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 topo_count: 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.
topo_count 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 topo_count 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 topo_count. 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.
topo_count 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