detect_tempo

EXPERIMENTAL automatic tempo (BPM) detection WITHOUT manual tapping. Detects beat onsets in live audio (kick band → RMS energy → moving-baseline threshold, reusing detect_onsets

SERVERtdmcp — TouchDesigner MCP server SOURCE@dpantani/tdmcp

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-pantani-tdmcp/detect-tempo.md

WHAT IT DOES

What detect_tempo does on tdmcp — TouchDesigner MCP server

AI agents call detect_tempo to retrieve information from tdmcp — TouchDesigner MCP server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why detect_tempo is rated Low

The tool reads and analyzes live audio data to detect BPM/tempo. It does not modify, create, delete, or trigger any external actions — it is purely an analytical/observational operation. Marked EXPERIMENTAL which slightly lowers confidence, but the description clearly describes a read/analysis operation with no side effects mentioned.

From the tool's definition 'automatic tempo (BPM) detection WITHOUT manual tapping. Detects beat onsets in live audio' — it analyzes/reads audio input and returns a tempo value

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs detect_tempo safely

PolicyLayer is an MCP gateway: it sits between your AI agents and tdmcp — TouchDesigner MCP server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For detect_tempo, this is the rule to start with:

detect_tempo Allowed

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

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect tdmcp — TouchDesigner MCP server, apply this rule, and every detect_tempo call is checked against it from then on.

FAQ

Questions about detect_tempo

What does the detect_tempo tool do? +

EXPERIMENTAL automatic tempo (BPM) detection WITHOUT manual tapping. Detects beat onsets in live audio (kick band → RMS energy → moving-baseline threshold, reusing detect_onsets. It is categorised as a Read tool in the tdmcp — TouchDesigner MCP server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on detect_tempo? +

Register the tdmcp — TouchDesigner MCP server MCP server in PolicyLayer and add a rule for detect_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 tdmcp — TouchDesigner MCP server. Nothing to install.

What risk level is detect_tempo? +

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

Can I rate-limit detect_tempo? +

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

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

detect_tempo is provided by the tdmcp — TouchDesigner MCP server MCP server (@dpantani/tdmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on tdmcp — TouchDesigner MCP server, and thousands of servers like it.

This server

All 334 tdmcp — TouchDesigner MCP server tools →

Across the catalogue

detect_slop on Slop Cop → The MCP Attack Database →

Guides

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