Low Risk

search_browser

Search the browser for items matching a query.

How to control search_browser ↓

What search_browser does on Ableton

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

Low Risk

Why search_browser needs a policy

This tool is a read-only operation that searches for items in a browser interface and returns results. It does not create, modify, delete, or execute code/commands. The low severity reflects the minimal risk even if misused—a search query cannot cause harm to the Ableton Live session or external systems.

From the tool's definition Tool performs a search operation ('search the browser for items matching a query'), which retrieves or queries data without modifying, deleting, or executing external operations. No side effects are described.

Documented attack patterns abuse exactly the kind of access search_browser gives an agent:

How to control search_browser

PolicyLayer is an MCP gateway — it sits between your AI agents and Ableton, and nothing reaches the server without passing your rules. This is the rule we recommend for search_browser:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "search_browser": {}
  }
}

search_browser is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Ableton — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about search_browser

What does the search_browser tool do? +

Search the browser for items matching a query. It is categorised as a Read tool in the Ableton MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on search_browser? +

Register the Ableton MCP server in PolicyLayer and add a rule for search_browser: 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 Ableton. Nothing to install.

What risk level is search_browser? +

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

Can I rate-limit search_browser? +

Yes. Add a rate_limit block to the search_browser 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 search_browser completely? +

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

search_browser is provided by the Ableton MCP server (jpoindexter/ableton-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Ableton tool call.

Start from Ableton, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

128 Ableton tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.