AI agents call scan_audio_folder to retrieve information from ReaperMCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Scanning a folder retrieves information about audio files without modifying, executing, or destroying data. Even though the description is empty (lowering confidence slightly), the tool name strongly indicates a Read operation: directory listing and file discovery. This poses minimal risk as it only exposes existing metadata about the file system.
From the tool's definition Tool name 'scan_audio_folder' indicates filesystem traversal and enumeration of audio files. No description provided, but the name and context among sibling analysis/creation tools suggests data retrieval without side effects.
Documented attack patterns abuse exactly the kind of access scan_audio_folder 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 scan_audio_folder:
{
"version": "1",
"default": "deny",
"tools": {
"scan_audio_folder": {}
}
}scan_audio_folder 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.
scan_audio_folder. It is categorised as a Read tool in the ReaperMCP MCP Server, which means it retrieves data without modifying state.
Register the Reaper MCP server in PolicyLayer and add a rule for scan_audio_folder: 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.
scan_audio_folder 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 scan_audio_folder 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 scan_audio_folder. 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.
scan_audio_folder 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.