set_rack_visible_macros
Set the Rack's visible_macro_count directly (1-16, Live 11+).
This record as markdown: /tools/io-github-dreamrec-livepilot/set-rack-visible-macros.md
What set_rack_visible_macros does on Livepilot
AI agents use set_rack_visible_macros to create or update resources in Livepilot, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Livepilot environment.
Why set_rack_visible_macros is rated Medium
This tool creates or modifies data reversibly within Ableton Live's session state. Setting visible_macro_count changes which macro controls are displayed on the rack interface, but this change is not destructive (can be undone/reverted) and does not delete data. It is not a Read operation because it has side effects (reconfigures the UI/state).
From the tool's definition 'Set the Rack's visible_macro_count directly' — modifies a configuration property of a Rack object in Ableton Live. The tool changes a rack parameter (visible_macro_count) from its current state to a new value (1-16).
Attacks that exploit this kind of access
The rule that runs set_rack_visible_macros 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 set_rack_visible_macros, this is the rule to start with:
set_rack_visible_macros stays usable, but capped: an agent stuck in a loop can't make hundreds of changes 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 set_rack_visible_macros call is checked against it from then on.
Questions about set_rack_visible_macros
Set the Rack's visible_macro_count directly (1-16, Live 11+). It is categorised as a Write tool in the Livepilot MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Livepilot MCP server in PolicyLayer and add a rule for set_rack_visible_macros: 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.
set_rack_visible_macros is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the set_rack_visible_macros 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 set_rack_visible_macros. 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.
set_rack_visible_macros 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.
This server
Across the catalogue