type_lyrics
AI agents invoke type_lyrics to trigger actions in Suno Autopilot MCP. 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.
The tool description is empty, lowering confidence. However, based on the server context (browser automation for Suno) and sibling tools (type_style, click_create), 'type_lyrics' almost certainly types lyrics into a browser form field as part of an automated browser interaction sequence. This is an Execute-category action (browser automation/UI interaction).
From the tool's definition Tool name 'type_lyrics' on a server that 'enables local AI models to automatically generate lyrics and style prompts, then submit songs to Suno via browser automation'; sibling tools include 'click_create', 'navigate_suno', 'type_style' suggesting browser…
Attacks that exploit this kind of access
type_lyrics. It is categorised as a Execute tool in the Suno Autopilot MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Suno Autopilot MCP server in PolicyLayer and add a rule for type_lyrics: 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 Suno Autopilot MCP. Nothing to install.
type_lyrics is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the type_lyrics 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 type_lyrics. 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.
type_lyrics is provided by the Suno Autopilot MCP server (voidreapercmxcix/suno-autopilot-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 →