delete_device

Delete a device from a track. Use undo to revert if needed.

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/delete-device.md

WHAT IT DOES

What delete_device does on Livepilot

AI agents call delete_device 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 delete_device is rated Critical

This tool irreversibly removes a device from an Ableton Live track. While the description mentions 'Use undo to revert if needed,' undo is a user-initiated recovery mechanism, not an inherent safety feature of the tool itself.

From the tool's definition Tool name is 'delete_device' and description states 'Delete a device from a track.' The verb 'delete' combined with removal of production assets (audio devices/plugins) is inherently destructive.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

delete_device Hidden

delete_device 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": [
    "delete_device"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about delete_device

What does the delete_device tool do? +

Delete a device from a track. Use undo to revert if needed. 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 delete_device? +

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

delete_device 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 delete_device? +

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

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

delete_device 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

sms_delete_message on Twilio SMS MCP Server →delete_snapshot on Why Did You Render →calendar_delete_event on Templonix Lite MCP Server →delete_addon_domain on cPanel MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

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