track_get_info

THE RISK

Low Risk

Why track_get_info needs a policy

This tool queries and returns track information from REAPER without creating, modifying, deleting, or executing any operations. It is a straightforward read-only operation with no side effects on the project or audio state.

From the tool's definition Tool name contains 'get' and description states 'Get detailed info for one track' - explicitly retrieves information without modification.

Documented attack patterns abuse exactly the kind of access track_get_info gives an agent:

POLICY

How to control track_get_info

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 track_get_info:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "track_get_info": {}
  }
}

track_get_info is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register ReaperMCP — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More ReaperMCP tools

Destructive envelope_clear_range envelope_clear_range Destructive fx_remove Remove FX from track chain. Destructive item_delete Delete an item. Destructive marker_delete Delete marker/region. Destructive midi_delete_all_notes Clear all notes from a MIDI item. Destructive midi_delete_cc Delete a CC event. Destructive midi_delete_note Delete a note. Destructive tempo_clear_all Delete every tempo/time-sig marker — resets the project to its base tempo.

All 138 ReaperMCP tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about track_get_info

What does the track_get_info tool do? +

Get detailed info for one track. It is categorised as a Read tool in the ReaperMCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on track_get_info? +

Register the Reaper MCP server in PolicyLayer and add a rule for track_get_info: 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.

What risk level is track_get_info? +

track_get_info is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit track_get_info? +

Yes. Add a rate_limit block to the track_get_info 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.

How do I block track_get_info completely? +

Set action: deny in the PolicyLayer policy for track_get_info. 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.

What MCP server provides track_get_info? +

track_get_info 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.

Enforce policy on every ReaperMCP tool call.

Start from ReaperMCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →