add_rack_macro

Add one macro to a Rack, raising visible_macro_count by 1 (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/add-rack-macro.md

WHAT IT DOES

What add_rack_macro does on Livepilot

AI agents use add_rack_macro 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.

RISK

Why add_rack_macro is rated Medium

This tool creates a new macro control on a Rack device, modifying the instrument's configuration. It is reversible (macros can be removed), produces side effects limited to the current Ableton session, and does not execute arbitrary code or delete data. The severity is medium because misconfiguration of macros could disrupt a music production workflow, but the change is localized and undo-able within the DAW.

From the tool's definition Tool description states 'Add one macro to a Rack, raising visible_macro_count by 1', which is a create/modify operation that changes state within Ableton Live.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

add_rack_macro Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "add_rack_macro": {
      "limits": [
        {
          "counter": "add_rack_macro_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Livepilot, apply this rule, and every add_rack_macro call is checked against it from then on.

FAQ

Questions about add_rack_macro

What does the add_rack_macro tool do? +

Add one macro to a Rack, raising visible_macro_count by 1 (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 add_rack_macro? +

Register the Livepilot MCP server in PolicyLayer and add a rule for add_rack_macro: 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 add_rack_macro? +

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

Can I rate-limit add_rack_macro? +

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

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

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

KEEP EXPLORING

More on Livepilot, and thousands of servers like it.

This server

All 474 Livepilot tools →

Across the catalogue

add-tag on Kanban MCP Server →kb_add on Persistent Kb → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →