render_project · Orpheus MCP: Risk & Policy

WHAT IT DOES

What render_project does on Orpheus

AI agents invoke render_project to trigger actions in Orpheus. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why render_project needs a policy

This tool triggers an external operation in REAPER (executing a render command via Main_OnCommand) that produces output files on disk. It is not purely reading data, nor is it destructive in the sense of deleting data, but it executes a DAW command that generates new audio files and may overwrite existing renders.

From the tool's definition Headless render to WAV/MP3 (RENDER_FILE + format/bounds + Main_OnCommand(41824))

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

render_project Rate-limited

render_project stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "render_project": {
      "limits": [
        {
          "counter": "render_project_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Orpheus, so you can run agents against it safely.

FAQ

Questions about render_project

What does the render_project tool do? +

Headless render to WAV/MP3 (RENDER_FILE + format/bounds + Main_OnCommand(41824)). It is categorised as a Execute tool in the Orpheus MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on render_project? +

Register the Orpheus MCP server in PolicyLayer and add a rule for render_project: 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 Orpheus. Nothing to install.

What risk level is render_project? +

render_project is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit render_project? +

Yes. Add a rate_limit block to the render_project 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 render_project completely? +

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

render_project is provided by the Orpheus MCP server (mal0ware/orpheus). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.