AI agents call analyze_groove to retrieve information from Orpheus without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs quantitative analysis on MIDI timing characteristics, producing metrics (swing percentage, tightness) derived from existing project data. No data is created, modified, deleted, or external operations triggered. It is purely observational/computational in nature, fitting the Read category (retrieves or queries data with no side effects).
From the tool's definition Tool description states 'Compute swing%% and tightness from raw MIDI PPQ onset deviation off the grid' — this is analysis and measurement of existing audio data.
Attacks that exploit this kind of access
Compute swing%% and tightness from raw MIDI PPQ onset deviation off the grid. It is categorised as a Read tool in the Orpheus MCP Server, which means it retrieves data without modifying state.
Register the Orpheus MCP server in PolicyLayer and add a rule for analyze_groove: 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.
analyze_groove 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 analyze_groove 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 analyze_groove. 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.
analyze_groove 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →