add_fx_by_name · Orpheus MCP: Risk & Policy

WHAT IT DOES

What add_fx_by_name does on Orpheus

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

WHY IT NEEDS A POLICY

Why add_fx_by_name needs a policy

Based on the tool name, it likely adds an audio effect (FX) to a track or project in REAPER by name, which is a reversible write/modify operation. The absence of a description lowers confidence, but 'add' strongly implies creating/modifying rather than reading or destructive action. Severity is medium as misuse could alter a music project's signal chain unexpectedly.

From the tool's definition Tool name 'add_fx_by_name' — no description provided.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

add_fx_by_name Rate-limited

add_fx_by_name 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_fx_by_name": {
      "limits": [
        {
          "counter": "add_fx_by_name_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 Orpheus, so you can run agents against it safely.

FAQ

Questions about add_fx_by_name

What does the add_fx_by_name tool do? +

add_fx_by_name. It is categorised as a Write tool in the Orpheus 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_fx_by_name? +

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

What risk level is add_fx_by_name? +

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

Can I rate-limit add_fx_by_name? +

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

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

add_fx_by_name is provided by the Orpheus MCP server (mal0ware/orpheus). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.