Get information about the Sushi transport state.
AI agents call get_transport_info 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 is a straightforward information retrieval operation with no side effects. It queries the transport state of the audio engine but does not execute commands, modify settings, delete data, or trigger external operations. The 'get' verb and 'information' language confirm read-only semantics. There is no ability to affect audio processing, MIDI routing, or any other audio configuration.
From the tool's definition Tool name 'get_transport_info' and description 'Get information about the Sushi transport state' indicate a read-only query operation that retrieves the current state of audio transport controls (play/stop/pause status, tempo, position, etc.) without…
Attacks that exploit this kind of access
Get information about the Sushi transport state. 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_transport_info: 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_transport_info 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_transport_info 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_transport_info. 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_transport_info 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 →