List all tempo + time-signature markers in the project.
AI agents call tempo_list_markers 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 queries and retrieves existing project metadata (tempo and time-signature markers) without modifying, creating, deleting, or executing any actions. It is a straightforward informational read operation with minimal blast radius if misused by an AI agent.
From the tool's definition Tool name 'tempo_list_markers' and description 'List all tempo + time-signature markers in the project' indicate a data retrieval operation with no side effects.
Documented attack patterns abuse exactly the kind of access tempo_list_markers 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 tempo_list_markers:
{
"version": "1",
"default": "deny",
"tools": {
"tempo_list_markers": {}
}
}tempo_list_markers 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.
List all tempo + time-signature markers in the project. 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 tempo_list_markers: 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.
tempo_list_markers 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 tempo_list_markers 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 tempo_list_markers. 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.
tempo_list_markers 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.