AI agents use set_fx_param 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.
This tool writes/modifies a parameter on an audio effect in a REAPER project. It changes project state but is reversible (parameters can be reset). It does not delete data, execute arbitrary code, or involve finances. Severity is medium because misuse could alter audio processing settings across a project, but the effect is non-destructive and recoverable.
From the tool's definition 'Set an FX parameter' — modifies an FX parameter value in the project using name-to-index resolution
Attacks that exploit this kind of access
Set an FX parameter with name→index resolution (so 'ratio' works, not just index 7). 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.
Register the Orpheus MCP server in PolicyLayer and add a rule for set_fx_param: 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.
set_fx_param is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the set_fx_param 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 set_fx_param. 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.
set_fx_param 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.
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 →