Delete a playlist you own. This action is IRREVERSIBLE. Args: - list_id: Playlist ID to delete (required) Returns: Deletion confirmation.
AI agents call neptime_delete_playlist to permanently remove resources in Neptime — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool permanently deletes a playlist with no possibility of recovery, as explicitly stated by 'IRREVERSIBLE'. This is a classic destructive operation with high blast radius if misused, potentially wiping out curated content collections.
From the tool's definition "Delete a playlist you own. This action is IRREVERSIBLE."
Attacks that exploit this kind of access
Delete a playlist you own. This action is IRREVERSIBLE. Args: - list_id: Playlist ID to delete (required) Returns: Deletion confirmation. It is categorised as a Destructive tool in the Neptime MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Neptime MCP server in PolicyLayer and add a rule for neptime_delete_playlist: 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 Neptime. Nothing to install.
neptime_delete_playlist is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the neptime_delete_playlist 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 neptime_delete_playlist. 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.
neptime_delete_playlist is provided by the Neptime MCP server (neptime-mcp-server). 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 →