save_processor_preset · Sushi MCP Server MCP: Risk & Policy

WHAT IT DOES

What save_processor_preset does on Sushi MCP Server

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

This tool creates or stores a new preset—a reversible operation that adds data to the system. It does not execute arbitrary code, delete data, move money, or trigger external side effects beyond preset storage. The blast radius is minimal: a saved preset can be deleted or overwritten. This is a straightforward Write operation.

From the tool's definition Tool is named 'save_processor_preset' and described as 'Save the current state of a processor as a preset.' The verb 'save' indicates data creation/storage. The action writes a new preset configuration to storage without destructive side effects.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

save_processor_preset Rate-limited

save_processor_preset 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": {
    "save_processor_preset": {
      "limits": [
        {
          "counter": "save_processor_preset_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 save_processor_preset

What does the save_processor_preset tool do? +

Save the current state of a processor as a preset. 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 save_processor_preset? +

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

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

Can I rate-limit save_processor_preset? +

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

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

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