tap_tempo

Tap the tempo (one tap). Live averages consecutive taps to set BPM.

SERVERLivepilot SOURCElivepilot

High RISK CLASS

Category Execute

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/tap-tempo.md

WHAT IT DOES

What tap_tempo does on Livepilot

AI agents invoke tap_tempo to trigger actions in Livepilot. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

RISK

Why tap_tempo is rated High

This tool triggers an external operation in Ableton Live — simulating a tempo tap input that affects the DAW's BPM setting. It's not a simple read, nor does it destroy data, but it executes an action in an external application (Live) that modifies the project's playback tempo state.

From the tool's definition Tap the tempo (one tap). Live averages consecutive taps to set BPM.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

tap_tempo Rate-limited

tap_tempo stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "tap_tempo": {
      "limits": [
        {
          "counter": "tap_tempo_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about tap_tempo

What does the tap_tempo tool do? +

Tap the tempo (one tap). Live averages consecutive taps to set BPM. It is categorised as a Execute tool in the Livepilot MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on tap_tempo? +

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

tap_tempo is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit tap_tempo? +

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

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

tap_tempo 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 → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →