List all saved presets.
AI agents call list_presets 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 performs a pure read operation—it retrieves and lists existing preset configurations from the Sushi audio engine. There are no side effects, no data modifications, and no external operations triggered. The minimal blast radius (listing presets cannot harm audio state or configuration) and non-destructive nature clearly place it in the Read category with low severity.
From the tool's definition Tool name 'list_presets' and description 'List all saved presets' indicate a query operation that retrieves and displays stored preset data without modifying, deleting, or executing any operations.
Attacks that exploit this kind of access
List all saved presets. 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 list_presets: 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.
list_presets 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 list_presets 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 list_presets. 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.
list_presets 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 →