remove_rack_macro

Remove the last macro from a Rack, lowering visible_macro_count by 1 (Live 11+).

SERVERLivepilot SOURCElivepilot

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-dreamrec-livepilot/remove-rack-macro.md

WHAT IT DOES

What remove_rack_macro does on Livepilot

AI agents call remove_rack_macro to permanently remove resources in Livepilot, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why remove_rack_macro is rated Critical

The tool removes a macro from a Rack device, which is a destructive operation that deletes configuration/parameter data. Removing a macro could break automation and assignments tied to it, and may not be easily reversible without undo history. The action is irreversible in the context of automated agent use.

From the tool's definition Remove the last macro from a Rack, lowering visible_macro_count by 1

Attacks that exploit this kind of access

RECOMMENDED RULE

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

remove_rack_macro Hidden

remove_rack_macro is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "remove_rack_macro"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about remove_rack_macro

What does the remove_rack_macro tool do? +

Remove the last macro from a Rack, lowering visible_macro_count by 1 (Live 11+). It is categorised as a Destructive tool in the Livepilot MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on remove_rack_macro? +

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

remove_rack_macro is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit remove_rack_macro? +

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

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

remove_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 → Critical-risk tools on this server →

Across the catalogue

remove_video on Mcptube Vision →remove_2fa on cPanel MCP Server →remove_concept on MegaMemory →task_assignees_remove on Vikunja → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Blast radius →Tool call approval →