Get all media items. Filter by track or -1 for all.
AI agents call item_get_all 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.
This tool retrieves or queries media items from the REAPER project without creating, modifying, deleting, or executing any actions. It has no side effects and fits the Read category definition: 'retrieves or queries data; no side effects (search, list, get, fetch)'. Low severity because unauthorized access to media item metadata poses minimal risk in a music production context.
From the tool's definition Tool name 'item_get_all' and description 'Get all media items' indicate data retrieval with no modification. The filtering capability (by track or -1 for all) is a read-only query operation.
Risk signalsBulk/mass operation — affects multiple targets
Documented attack patterns abuse exactly the kind of access item_get_all 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_get_all:
{
"version": "1",
"default": "deny",
"tools": {
"item_get_all": {}
}
}item_get_all 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 all media items. Filter by track or -1 for all. 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 item_get_all: 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_get_all 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 item_get_all 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_get_all. 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_get_all 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.