dfs_search
Depth-first search on a graph. Finds a path, visit order, reachable count, and detects cycles.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/dfs-search.md
What dfs_search does on UnClick
AI agents call dfs_search 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 | Array of edges |
start | string | Yes | Start node |
target | string | — | Optional target node |
directed | boolean | — | Whether the graph is directed (default true) |
Parameters from the server's own tool schema.
Why dfs_search is rated Low
This is a graph traversal algorithm that retrieves and analyzes properties of a graph data structure. It performs read-only operations (searching, counting, cycle detection) without creating, modifying, deleting, or executing external operations. No data is altered and no side effects occur.
From the tool's definition Tool description states it 'Finds a path, visit order, reachable count, and detects cycles' — purely informational queries on graph structure with no mutations or side effects.
Attacks that exploit this kind of access
The rule that runs dfs_search 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 dfs_search, this is the rule to start with:
dfs_search 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 dfs_search call is checked against it from then on.
Questions about dfs_search
Depth-first search on a graph. Finds a path, visit order, reachable count, and detects cycles. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
dfs_search accepts 4 parameters: edges, start, target, directed. Required: edges, start. 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 dfs_search: 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.
dfs_search 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 dfs_search 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 dfs_search. 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.
dfs_search 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