add_processor_to_track · Sushi MCP Server MCP: Risk & Policy

WHAT IT DOES

What add_processor_to_track does on Sushi MCP Server

AI agents use add_processor_to_track 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 add_processor_to_track needs a policy

This tool modifies audio track state by adding a processor, which is reversible (the sibling tool delete_processor and disconnect operations confirm processors can be removed). The action has bounded scope (one track) and medium severity—misconfiguration could degrade audio quality or create feedback, but effects are not permanent and can be undone via delete_processor.

From the tool's definition add_processor_to_track creates a new processor instance on an audio track, modifying the track's configuration and signal chain. This is a creation/modification action without data deletion or financial impact.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

add_processor_to_track Rate-limited

add_processor_to_track 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": {
    "add_processor_to_track": {
      "limits": [
        {
          "counter": "add_processor_to_track_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 add_processor_to_track

What does the add_processor_to_track tool do? +

Add a processor to a track. 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 add_processor_to_track? +

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

What risk level is add_processor_to_track? +

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

Can I rate-limit add_processor_to_track? +

Yes. Add a rate_limit block to the add_processor_to_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.

How do I block add_processor_to_track completely? +

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

What MCP server provides add_processor_to_track? +

add_processor_to_track 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.