New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

load_browser_item

A execute tool on the Livepilot MCP server.

SERVERLivepilot SOURCElivepilot
High RISK CLASS
Category Execute
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

Questions about load_browser_item

What does the load_browser_item tool do? +

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.

How do I enforce a policy on load_browser_item? +

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.

What risk level is load_browser_item? +

load_browser_item is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit load_browser_item? +

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.

How do I block load_browser_item completely? +

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.

What MCP server provides load_browser_item? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Livepilot's. Pull the full record:

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.