connect_track_to_output · Sushi MCP Server MCP

WHAT IT DOES

What connect_track_to_output does on Sushi MCP Server

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

WHY IT NEEDS A POLICY

Why connect_track_to_output needs a policy

This tool creates a connection between a track and an output channel in the audio engine. It is a reversible configuration change (Write), as the connection can presumably be disconnected later. It does not delete data or execute arbitrary code, and has no financial implications. Misuse could disrupt audio routing but is recoverable.

From the tool's definition Connect a track to an output channel

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

connect_track_to_output Rate-limited

connect_track_to_output 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": {
    "connect_track_to_output": {
      "limits": [
        {
          "counter": "connect_track_to_output_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Sushi MCP Server, so you can run agents against it safely.

FAQ

Questions about connect_track_to_output

What does the connect_track_to_output tool do? +

Connect a track to an output channel. It is categorised as a Write tool in the Sushi MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on connect_track_to_output? +

Register the Sushi MCP Server MCP server in PolicyLayer and add a rule for connect_track_to_output: 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 Sushi MCP Server. Nothing to install.

What risk level is connect_track_to_output? +

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

Can I rate-limit connect_track_to_output? +

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

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

connect_track_to_output is provided by the Sushi MCP Server MCP server (nagarjun226/sushi-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.