bypass_processor · Sushi MCP Server MCP: Risk & Policy

WHAT IT DOES

What bypass_processor does on Sushi MCP Server

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

Bypassing or enabling a processor changes its active state within the audio engine. This is a reversible write operation (it can be toggled back), not destructive or financial. Misuse could disrupt audio processing pipelines, hence medium severity.

From the tool's definition 'Bypass or enable a processor' — toggles the bypass state of an audio processor, which is a reversible modification to the audio processing chain.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

bypass_processor Rate-limited

bypass_processor 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": {
    "bypass_processor": {
      "limits": [
        {
          "counter": "bypass_processor_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 bypass_processor

What does the bypass_processor tool do? +

Bypass or enable a processor. 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 bypass_processor? +

Register the Sushi MCP Server MCP server in PolicyLayer and add a rule for bypass_processor: 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 bypass_processor? +

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

Can I rate-limit bypass_processor? +

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

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

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