Upload a video to Neptime.io through the live /videos/upload endpoint. Provide either video_path for a local file available to the MCP server, or video_base64 plus video_filename. Videos can be mp4, mov, webm, mpeg, avi, or mkv. The default privacy is private (1) for safety. Args: - title: Video ...
AI agents use neptime_upload_video 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 is a Write operation—it creates new video content and persists it on Neptime.io. While upload is a creation action, it is reversible (videos can be deleted as evidenced by sibling tools like neptime_delete_article and neptime_delete_playlist).
From the tool's definition Tool uploads and creates video content through the /videos/upload endpoint with required parameters (title, description, tags) and file sources (video_path or video_base64). This creates new persistent data on the platform.
Attacks that exploit this kind of access
Upload a video to Neptime.io through the live /videos/upload endpoint. Provide either video_path for a local file available to the MCP server, or video_base64 plus video_filename. Videos can be mp4, mov, webm, mpeg, avi, or mkv. The default privacy is private (1) for safety. Args: - title: Video title (required) - description: Video description (required) - tags: Comma-separated tags (required) - video_path OR video_base64: Video file source (required) - video_filename: Filename when using video_base64 - thumbnail_path OR thumbnail_base64: Optional thumbnail - category_id: Optional category ID - privacy: 0=public, 1=private, 2=unlisted (default: 1) - age_restriction: 1=all ages, 2=18+ (default: 1) - is_short: true for short-form video (default: false) Returns: Uploaded video object with video_id, URL, stream URL, thumbnail, approval status, and privacy. 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_upload_video: 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_upload_video 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_upload_video 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_upload_video. 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_upload_video 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 →