Set fade in/out. -1=unchanged.
AI agents use item_set_fade to create or update resources in ReaperMCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ReaperMCP environment.
This tool modifies audio fade properties on a track item, which is a reversible change to project data. It does not execute arbitrary code, delete content, or move money, placing it in the Write category. Severity is medium because incorrect fade settings could degrade audio quality or require manual correction, but the change is easily undone by setting different fade values or using undo functionality in REAPER.
From the tool's definition Tool name is `item_set_fade` and description states 'Set fade in/out', indicating modification of audio properties. The -1 parameter convention suggests it modifies existing audio item properties (fade envelope) reversibly.
Documented attack patterns abuse exactly the kind of access item_set_fade gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and ReaperMCP, and nothing reaches the server without passing your rules. This is the rule we recommend for item_set_fade:
{
"version": "1",
"default": "deny",
"tools": {
"item_set_fade": {
"limits": [
{
"counter": "item_set_fade_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}item_set_fade 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.
Free to start. No card required.
Set fade in/out. -1=unchanged. It is categorised as a Write tool in the ReaperMCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Reaper MCP server in PolicyLayer and add a rule for item_set_fade: 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 ReaperMCP. Nothing to install.
item_set_fade 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 item_set_fade 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 item_set_fade. 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.
item_set_fade is provided by the Reaper MCP server (xdarkzx/reaper-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from ReaperMCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
138 ReaperMCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.