AI agents use dsl_marker to create or update resources in REAPER MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your REAPER MCP Server environment.
Markers in REAPER are metadata objects that organize and navigate projects. Creating or modifying markers is a reversible Write operation—not Read (no query indicated), not Execute (doesn't run arbitrary code), not Destructive (markers can be removed without permanent data loss), not Financial. The tool likely creates or edits markers based on naming conventions of sibling tools.
From the tool's definition Tool name 'dsl_marker' suggests marker creation/management in REAPER DAW. Sibling tools like 'dsl_create_bus', 'dsl_create_send', 'dsl_automate' are all Write operations that modify project state.
Documented attack patterns abuse exactly the kind of access dsl_marker gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and REAPER MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for dsl_marker:
{
"version": "1",
"default": "deny",
"tools": {
"dsl_marker": {
"limits": [
{
"counter": "dsl_marker_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}dsl_marker stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
dsl_marker. It is categorised as a Write tool in the REAPER MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the REAPER MCP Server MCP server in PolicyLayer and add a rule for dsl_marker: 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 MCP Server. Nothing to install.
dsl_marker is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the dsl_marker 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 dsl_marker. 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.
dsl_marker is provided by the REAPER MCP Server MCP server (shiehn/total-reaper-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 45 REAPER MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
45 REAPER MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.