reset_tuning_system

Reset all per-degree tuning offsets to 12-TET (Live 12.1+).

SERVERLivepilot SOURCElivepilot

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-dreamrec-livepilot/reset-tuning-system.md

WHAT IT DOES

What reset_tuning_system does on Livepilot

AI agents use reset_tuning_system to create or update resources in Livepilot, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Livepilot environment.

RISK

Why reset_tuning_system is rated Medium

This tool modifies tuning settings by resetting all per-degree offsets back to the standard 12-TET system. It is a write/modify operation on project settings. While it overwrites current tuning customizations (which could be significant creative work), it resets to a well-defined default state rather than deleting data irreversibly — the user could re-enter their custom tuning values.

From the tool's definition Reset all per-degree tuning offsets to 12-TET

Attacks that exploit this kind of access

RECOMMENDED RULE

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

reset_tuning_system Rate-limited

reset_tuning_system stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "reset_tuning_system": {
      "limits": [
        {
          "counter": "reset_tuning_system_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Livepilot, apply this rule, and every reset_tuning_system call is checked against it from then on.

FAQ

Questions about reset_tuning_system

What does the reset_tuning_system tool do? +

Reset all per-degree tuning offsets to 12-TET (Live 12.1+). It is categorised as a Write tool in the Livepilot MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on reset_tuning_system? +

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

reset_tuning_system is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit reset_tuning_system? +

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

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

reset_tuning_system 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

Govern customer-ops agents →Argument validation →Scoped token →