identify_scale

Identify the scale/mode of a MIDI clip beyond basic major/minor.

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/identify-scale.md

WHAT IT DOES

What identify_scale does on Livepilot

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

This tool reads/analyzes MIDI clip data to identify musical scale or mode. It performs analysis only, returning information without modifying any data, making it a Read operation with low blast radius.

From the tool's definition "Identify the scale/mode of a MIDI clip" — purely analytical/query operation with no side effects

Attacks that exploit this kind of access

RECOMMENDED RULE

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

identify_scale Allowed

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

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

FAQ

Questions about identify_scale

What does the identify_scale tool do? +

Identify the scale/mode of a MIDI clip beyond basic major/minor. 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 identify_scale? +

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

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

Can I rate-limit identify_scale? +

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

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

identify_scale 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

The MCP Attack Database →

Guides

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