This record as markdown: /tools/io-github-dave-london-pare-search/tree.md
What tree does on Search
AI agents call tree to retrieve information from Search without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why tree is rated Low
This tool queries and displays dependency information from a Rust project's manifest file(s). It has no side effects, makes no modifications to the project, and does not execute code or external operations. It is purely a read operation that retrieves and formats existing metadata for display.
From the tool's definition The tool 'Displays the dependency tree' is a retrieval operation that reads and presents existing project metadata. It performs no data modification, deletion, or code execution. The description explicitly indicates a read-only informational function.
Attacks that exploit this kind of access
The rule that runs tree safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Search, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For tree, this is the rule to start with:
tree 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 Search, apply this rule, and every tree call is checked against it from then on.
Questions about tree
Displays the dependency tree for a Rust project. It is categorised as a Read tool in the Search MCP Server, which means it retrieves data without modifying state.
Register the Search MCP server in PolicyLayer and add a rule for tree: 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 Search. Nothing to install.
tree 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 tree 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 tree. 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.
tree is provided by the Search MCP server (Dave-London/Pare). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Search, and thousands of servers like it.
This server
Across the catalogue