master_track
AI agents invoke master_track to trigger actions in Tonn MCP Server. 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.
Mastering a track is an external operation that processes and transforms audio files via the RoEx Tonn API. This falls under Execute (triggers external operations). The description is empty, lowering confidence. Severity is high because misuse could process unintended audio files or consume API credits, and the operation may be difficult to reverse depending on how results are stored.
From the tool's definition Tool name 'master_track' on a server described as enabling AI assistants to 'mix, master, and analyze audio using the RoEx Tonn API'. The name implies triggering an audio mastering operation via the external RoEx Tonn API.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
master_track. It is categorised as a Execute tool in the Tonn MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Tonn MCP Server MCP server in PolicyLayer and add a rule for master_track: 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 Tonn MCP Server. Nothing to install.
master_track is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the master_track 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.
Set action: deny in the PolicyLayer policy for master_track. 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.
master_track is provided by the Tonn MCP Server MCP server (roex-audio/tonn-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →