splice_list_collections

A read tool on the Livepilot MCP server.

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/splice-list-collections.md

WHAT IT DOES

What splice_list_collections does on Livepilot

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

The tool appears to retrieve or enumerate collections from Splice (a music collaboration platform integrated with Ableton Live). No description was provided, which reduces confidence slightly, but the naming convention strongly suggests a read-only query operation that retrieves existing data without side effects.

From the tool's definition Tool name 'splice_list_collections' indicates a list/query operation. The 'list' verb and context of retrieving Splice collections suggest data retrieval without modification.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

splice_list_collections Allowed

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

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

FAQ

Questions about splice_list_collections

What does the splice_list_collections tool do? +

splice_list_collections is a read tool on the Livepilot MCP server. 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 splice_list_collections? +

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

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

Can I rate-limit splice_list_collections? +

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

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

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