Remove a processor from a track.
AI agents call remove_processor_from_track to permanently remove resources in Sushi MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Removing a processor from a track destroys its association, configuration, and any unsaved state. This is not a simple write/update but an irreversible removal. Given the audio engine context, this could disrupt live audio processing pipelines. Ranked Destructive over Write because the action cannot be simply undone without re-adding and reconfiguring the processor.
From the tool's definition 'Remove a processor from a track' — removing a processor is an irreversible deletion of that processor's configuration, routing, and state from the track.
Attacks that exploit this kind of access
Remove a processor from a track. It is categorised as a Destructive tool in the Sushi MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Sushi MCP Server MCP server in PolicyLayer and add a rule for remove_processor_from_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.
remove_processor_from_track is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the remove_processor_from_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 remove_processor_from_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.
remove_processor_from_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.
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 →