list_open_creative_threads

List all open (non-stale) creative threads in the session.

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/list-open-creative-threads.md

WHAT IT DOES

What list_open_creative_threads does on Livepilot

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

This tool queries and returns information about creative threads in an Ableton Live session. It performs no writes, deletions, code execution, or financial transactions. The blast radius is minimal—misuse would only expose session metadata that is already visible within the application.

From the tool's definition Tool name uses 'list' verb and description states 'List all open (non-stale) creative threads' — a pure retrieval operation with no modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

list_open_creative_threads Allowed

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

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

FAQ

Questions about list_open_creative_threads

What does the list_open_creative_threads tool do? +

List all open (non-stale) creative threads in the session. 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 list_open_creative_threads? +

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

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

Can I rate-limit list_open_creative_threads? +

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

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

list_open_creative_threads 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

aiva_list_affiliates on AIVA MCP Server →list_circuits on 0gzk →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

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