AI agents call get_fx_params to retrieve information from Orpheus without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only reads the current state of audio effects parameters in a REAPER project. It does not modify audio, apply changes, execute code, or delete anything. Although it operates within an audio production context, its function is purely informational—extracting human-readable parameter data from an opaque format. This is a classic Read operation with minimal blast radius.
From the tool's definition The tool description explicitly states it 'Decode[s] an FX chain's parameters BY NAME', retrieving parameter values from an existing effect chain without modifying them.
Attacks that exploit this kind of access
Decode an FX chain's parameters BY NAME (e.g. compressor ratio), not as opaque 0–1. It is categorised as a Read tool in the Orpheus MCP Server, which means it retrieves data without modifying state.
Register the Orpheus MCP server in PolicyLayer and add a rule for get_fx_params: 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.
get_fx_params is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_fx_params 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 get_fx_params. 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.
get_fx_params 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 →