AI agents call get_markers to retrieve information from Reaper without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves marker information from the REAPER project without modifying, deleting, or executing any operations. It is a pure read operation that queries project state. The blast radius of misuse is minimal—an AI agent cannot cause harm by reading markers. Low severity and high confidence are appropriate for a simple data retrieval function.
From the tool's definition Tool name is 'get_markers' and description states 'Get all markers in the project' - uses 'Get' verb and retrieves existing data with no modification or side effects.
Documented attack patterns abuse exactly the kind of access get_markers gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Reaper, and nothing reaches the server without passing your rules. This is the rule we recommend for get_markers:
{
"version": "1",
"default": "deny",
"tools": {
"get_markers": {}
}
}get_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.
Get all markers in the project. It is categorised as a Read tool in the Reaper MCP Server, which means it retrieves data without modifying state.
Register the Reaper MCP server in PolicyLayer and add a rule for get_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 Reaper. Nothing to install.
get_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 get_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 get_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.
get_markers is provided by the Reaper MCP server (twelvetake-studios/reaper-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Reaper, 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.
158 Reaper tools catalogued and risk-classified — across an index of 43,000+ MCP servers.