get_playing_clips

Get all currently playing or triggered clips.

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-playing-clips.md

WHAT IT DOES

What get_playing_clips does on Livepilot

AI agents call get_playing_clips 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_playing_clips is rated Low

This tool retrieves information about clips that are currently active in Ableton Live. It queries the state of the music production software without modifying, creating, deleting, or executing operations. The verb 'Get' and the passive observation of clip status confirm this is a read-only information retrieval operation with no side effects.

From the tool's definition Tool name is 'get_playing_clips' and description states 'Get all currently playing or triggered clips' — uses verb 'Get' which indicates retrieval/query operation with no state modification.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

get_playing_clips Allowed

get_playing_clips 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_playing_clips": {}
  }
}

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_playing_clips call is checked against it from then on.

FAQ

Questions about get_playing_clips

What does the get_playing_clips tool do? +

Get all currently playing or triggered clips. 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_playing_clips? +

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

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

Can I rate-limit get_playing_clips? +

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

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

get_playing_clips 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 →