Create a new playlist. Limit: 100 playlists max per user. Args: - name: Playlist name, 2-100 chars (required) - description: Description, max 500 chars (optional) - privacy: public, private, or unlisted (default: private) Returns: Created playlist object.
AI agents use neptime_create_playlist to create or update resources in Neptime — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Neptime environment.
This tool creates a new playlist, which is a reversible operation (playlists can be deleted, as evidenced by the sibling tool 'neptime_delete_playlist'). It does not execute code, move money, or permanently destroy data. The blast radius is minimal—a user can create up to 100 playlists, and any created playlist can be removed. This is a standard Write operation.
From the tool's definition Tool name 'neptime_create_playlist' and description 'Create a new playlist' indicate creation of new data. Arguments allow setting playlist name, description, and privacy settings. Return value is 'Created playlist object' confirming successful data creation.
Attacks that exploit this kind of access
Create a new playlist. Limit: 100 playlists max per user. Args: - name: Playlist name, 2-100 chars (required) - description: Description, max 500 chars (optional) - privacy: public, private, or unlisted (default: private) Returns: Created playlist object. It is categorised as a Write tool in the Neptime MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Neptime MCP server in PolicyLayer and add a rule for neptime_create_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_create_playlist is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the neptime_create_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_create_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_create_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 →