get_device_presets

List available presets for an Ableton device (e.g. 'Corpus', 'Drum Buss', 'Wavetable').

SERVERLivepilot SOURCElivepilot

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-dreamrec-livepilot/get-device-presets.md

WHAT IT DOES

What get_device_presets does on Livepilot

AI agents call get_device_presets to retrieve information from Livepilot without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why get_device_presets is rated Low

This tool retrieves preset names from Ableton Live without modifying state, executing code, or causing irreversible changes. It is a simple data retrieval operation analogous to a GET request or list operation.

From the tool's definition Tool description: 'List available presets for an Ableton device'. The verb 'List' and the action of retrieving/enumerating presets indicates a read-only query with no data modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

get_device_presets Allowed

get_device_presets is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_device_presets": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about get_device_presets

What does the get_device_presets tool do? +

List available presets for an Ableton device (e.g. 'Corpus', 'Drum Buss', 'Wavetable'). It is categorised as a Read tool in the Livepilot MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_device_presets? +

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

get_device_presets is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_device_presets? +

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

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

get_device_presets 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

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →