explain_style · Orpheus MCP: Risk & Policy

WHAT IT DOES

What explain_style does on Orpheus

AI agents invoke explain_style 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 explain_style needs a policy

explain_style executes analysis operations on a live music project that depend on the project's audio content and parameters. While framed as explanatory, it performs computational operations that could trigger external effects or data transformations in REAPER's state. This is Execute rather than Read because it 'runs' thresholds (active computation) rather than passively retrieving static information.

From the tool's definition Tool description states 'run feature thresholds over the current project' — 'run' indicates code/analysis execution on the active REAPER project with side effects dependent on project state.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

explain_style Rate-limited

explain_style 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": {
    "explain_style": {
      "limits": [
        {
          "counter": "explain_style_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 explain_style

What does the explain_style tool do? +

"Why does this sound like X?" — run feature thresholds over the current project and. 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 explain_style? +

Register the Orpheus MCP server in PolicyLayer and add a rule for explain_style: 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 explain_style? +

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

Can I rate-limit explain_style? +

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

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

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