This record as markdown: /tools/io-github-dreamrec-livepilot/build-song-brain.md
What build_song_brain does on Livepilot
AI agents invoke build_song_brain 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 build_song_brain is rated High
The tool name indicates an action ('build') that constructs or initializes something ('song_brain'), consistent with Execute-category tools that trigger operations whose effects depend on runtime arguments. While the empty description reduces certainty, the context of an Ableton Live copilot with 91 production tools suggests this performs an operation beyond simple data retrieval.
From the tool's definition Tool name 'build_song_brain' suggests construction or initialization of a complex state object within Ableton Live.
Attacks that exploit this kind of access
The rule that runs build_song_brain 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 build_song_brain, this is the rule to start with:
build_song_brain 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 build_song_brain call is checked against it from then on.
Questions about build_song_brain
build_song_brain 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 build_song_brain: 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.
build_song_brain 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 build_song_brain 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 build_song_brain. 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.
build_song_brain 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