get_browser_tree
Get an overview of browser categories and their children.
This record as markdown: /tools/io-github-dreamrec-livepilot/get-browser-tree.md
What get_browser_tree does on Livepilot
AI agents call get_browser_tree to retrieve information from Livepilot without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_browser_tree is rated Low
This tool queries the browser structure in Ableton Live to retrieve organizational metadata about categories. The verb 'Get' and the passive construction 'Get an overview' confirm it is a read-only operation with no side effects. It has minimal blast radius—exposure would only allow an agent to enumerate the browser structure, which is non-sensitive production metadata.
From the tool's definition Tool name 'get_browser_tree' and description 'Get an overview of browser categories and their children' indicate a retrieval operation that returns hierarchical data without modification.
Attacks that exploit this kind of access
The rule that runs get_browser_tree safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Livepilot, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_browser_tree, this is the rule to start with:
get_browser_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 Livepilot, apply this rule, and every get_browser_tree call is checked against it from then on.
Questions about get_browser_tree
Get an overview of browser categories and their children. It is categorised as a Read tool in the Livepilot MCP Server, which means it retrieves data without modifying state.
Register the Livepilot MCP server in PolicyLayer and add a rule for get_browser_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 Livepilot. Nothing to install.
get_browser_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 get_browser_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 get_browser_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.
get_browser_tree is provided by the Livepilot MCP server (livepilot). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Livepilot, and thousands of servers like it.
This server
Across the catalogue