AI agents call get_fx_list to retrieve information from Reaper Reapy without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool appears to retrieve or list FX (audio effects) information from REAPER DAW, consistent with Read category operations (get, list, fetch). No modification, deletion, or execution of code/commands is implied. The empty description reduces confidence slightly, but the name and position among write/destructive siblings supports classification as a read-only query.
From the tool's definition Tool name 'get_fx_list' indicates retrieval of effects list data. Description is empty, but naming convention and context among sibling tools (which include destructive operations like delete_item and delete_marker) suggests this is a query/retrieval…
Documented attack patterns abuse exactly the kind of access get_fx_list gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Reaper Reapy, and nothing reaches the server without passing your rules. This is the rule we recommend for get_fx_list:
{
"version": "1",
"default": "deny",
"tools": {
"get_fx_list": {}
}
}get_fx_list is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
get_fx_list. It is categorised as a Read tool in the Reaper Reapy MCP Server, which means it retrieves data without modifying state.
Register the Reaper Reapy MCP server in PolicyLayer and add a rule for get_fx_list: 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 Reaper Reapy. Nothing to install.
get_fx_list 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_list 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_list. 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_list is provided by the Reaper Reapy MCP server (wegitor/reaper-reapy-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 47 Reaper Reapy tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
47 Reaper Reapy tools catalogued and risk-classified — across an index of 42,500+ MCP servers.