This record as markdown: /tools/io-github-dreamrec-livepilot/load-browser-item.md
What load_browser_item does on Livepilot
AI agents invoke load_browser_item to trigger actions in Livepilot. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why load_browser_item is rated High
In Ableton Live, loading a browser item typically triggers an action that instantiates a plugin, sample, or device into the session — this is an Execute-level operation as it triggers an external operation in the DAW. However, since the description is empty, confidence is reduced. It could also be interpreted as Write (placing an item).
From the tool's definition Tool name 'load_browser_item' suggests loading/executing a browser item into the DAW environment; description is empty and uninformative.
Attacks that exploit this kind of access
The rule that runs load_browser_item 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 load_browser_item, this is the rule to start with:
load_browser_item stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. 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 load_browser_item call is checked against it from then on.
Questions about load_browser_item
load_browser_item is a execute tool on the Livepilot MCP server. It is categorised as a Execute tool in the Livepilot MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Livepilot MCP server in PolicyLayer and add a rule for load_browser_item: 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.
load_browser_item is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the load_browser_item 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 load_browser_item. 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.
load_browser_item 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.
Across the catalogue