search_samples

What search_samples does on Livepilot

AI agents call search_samples 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 search_samples is rated Low

Search operations are inherently read-only—they retrieve or query data with no side effects. Even within a music production context where Ableton samples could be part of the project state, a search function merely locates and returns sample metadata or references without creating, modifying, deleting, or executing anything. The low severity reflects minimal blast radius if an AI agent performs unnecessary searches.

From the tool's definition Tool name 'search_samples' indicates a query/retrieval operation. The description is empty, limiting direct evidence, but the name strongly suggests searching through a sample library without modification.

The rule that runs search_samples 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 search_samples, this is the rule to start with:

{
  "version": "1",
  "default": "deny",
  "tools": {
    "search_samples": {}
  }
}

Questions about search_samples