get_tool_tree

获取工具节点和下一层子节点的工具名称的方法,每次调用仅获取一层子节点,主要用于列出某个模块的方法和获取所有方法列表。 参数说明: - name: 要查询的节点名称,并根据name返回该节点及其下一层节点,不传则返回根节点和下一层结构。 返回结构是一个序列化树状结构的json,其中- Name: 节点名称,root表示根节点,其他为具体的库名、类名或方法名 - Type: 节点类型,包含: root(根节点)、directory(库目录)、class(工具类)、tool(具体方法) - Belong: 父节点名称,标识该节点属于哪个上级节点 - Children: 子节点列表,仅包含该节点...

Server Leaper Vision Toolkit leaper-mcp/leaper-mcp-proxy
Category Read
Risk class Low
Parameters 10 required

What get_tool_tree does on Leaper Vision Toolkit

AI agents call get_tool_tree to retrieve information from Leaper Vision Toolkit without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

ParameterTypeRequiredDescription
name string 要查询的节点名称,不传则返回根节点下面的下一层结构

Parameters from the server's own tool schema.

Why get_tool_tree needs a policy

This is a read-only introspection/discovery tool that queries and returns metadata about available tools and their hierarchy. It has no side effects, does not modify state, and merely retrieves structural information about the toolkit's interface.

From the tool's definition Tool description states it is a method to 'retrieve tool node names and next-level child node tool names' (获取工具节点和下一层子节点的工具名称的方法) and 'list methods of a module and get all method lists' (主要用于列出某个模块的方法和获取所有方法列表).

Risk signalsAdmin/system-level operation

Questions about get_tool_tree

What does the get_tool_tree tool do? +

获取工具节点和下一层子节点的工具名称的方法,每次调用仅获取一层子节点,主要用于列出某个模块的方法和获取所有方法列表。 参数说明: - name: 要查询的节点名称,并根据name返回该节点及其下一层节点,不传则返回根节点和下一层结构。 返回结构是一个序列化树状结构的json,其中- Name: 节点名称,root表示根节点,其他为具体的库名、类名或方法名 - Type: 节点类型,包含: root(根节点)、directory(库目录)、class(工具类)、tool(具体方法) - Belong: 父节点名称,标识该节点属于哪个上级节点 - Children: 子节点列表,仅包含该节点下的子项,不包含该节点的子节点的所有子项. It is categorised as a Read tool in the Leaper Vision Toolkit MCP Server, which means it retrieves data without modifying state.

What parameters does get_tool_tree accept? +

get_tool_tree accepts 1 parameter: name. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on get_tool_tree? +

Register the Leaper Vision Toolkit MCP server in PolicyLayer and add a rule for get_tool_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 Leaper Vision Toolkit. Nothing to install.

What risk level is get_tool_tree? +

get_tool_tree is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_tool_tree? +

Yes. Add a rate_limit block to the get_tool_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.

How do I block get_tool_tree completely? +

Set action: deny in the PolicyLayer policy for get_tool_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.

What MCP server provides get_tool_tree? +

get_tool_tree is provided by the Leaper Vision Toolkit MCP server (leaper-mcp/leaper-mcp-proxy). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER SERVER

Every MCP server has a record like this.

Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.