Get all processors on a track.
AI agents call get_track_processors to retrieve information from Sushi MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves information about processors currently assigned to a track without modifying, executing, or deleting anything. It has no side effects and poses minimal risk even if an AI agent invokes it; the worst outcome would be querying information that may already be visible or attempting repeated queries, neither of which causes harm.
From the tool's definition Tool name 'get_track_processors' and description 'Get all processors on a track' indicate a retrieval operation with no side effects. The verb 'get' and the context of querying processor information on an audio track confirm this is a read-only query.
Attacks that exploit this kind of access
Get all processors on a track. It is categorised as a Read tool in the Sushi MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Sushi MCP Server MCP server in PolicyLayer and add a rule for get_track_processors: 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 Sushi MCP Server. Nothing to install.
get_track_processors 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_track_processors 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_track_processors. 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_track_processors is provided by the Sushi MCP Server MCP server (nagarjun226/sushi-mcp). 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 →