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

set_rack_visible_macros

Set the Rack's visible_macro_count directly (1-16, Live 11+).

SERVERLivepilot SOURCElivepilot
Medium RISK CLASS
Category Write
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/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).

Questions about set_rack_visible_macros

What does the set_rack_visible_macros tool do? +

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.

How do I enforce a policy on set_rack_visible_macros? +

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.

What risk level is set_rack_visible_macros? +

set_rack_visible_macros is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit set_rack_visible_macros? +

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.

How do I block set_rack_visible_macros completely? +

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.

What MCP server provides set_rack_visible_macros? +

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.

// 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.