scan_full_library

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/scan-full-library.md

WHAT IT DOES

What scan_full_library does on Livepilot

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

Based on naming convention alone, 'scan_full_library' appears to read and possibly index Ableton Live's media library. No description is available, which lowers confidence slightly, but the semantic context (sibling tools include 'analyze_composition' and 'analyze_harmony') and the name's passive inspection nature suggest this is a Read operation.

From the tool's definition Tool name 'scan_full_library' suggests a query/enumeration operation over a music library. The verb 'scan' typically implies data retrieval without modification.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

scan_full_library Allowed

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

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

FAQ

Questions about scan_full_library

What does the scan_full_library tool do? +

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

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

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

Can I rate-limit scan_full_library? +

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

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

scan_full_library 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

detect_slop_full on Slop Cop → The MCP Attack Database →

Guides

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