8 tools from the Vugola MCP Server, categorised by risk level.
View the Vugola policy →download_clip Download a rendered clip to the user's local Downloads folder (or a configured directory). Returns the saved file path and size in bytes. Use this ... get_clip_status Check whether a clipping job is done. Call this when the user asks about a job they've already started. get_usage Return how many credits the user has, their plan, and how many they've used this month. list_scheduled_posts List scheduled social posts. Optional filters: status ('scheduled' | 'processing' | 'posted' | 'failed'), platform, limit (default 20, max 100), of... caption_video Add captions to a short video (up to 5 minutes). Ask the user for aspect_ratio and caption_style if they're not given. If the user says 'just pick,... 2/5 schedule_post Schedule clips or media to post on supported social platforms. Ask the user for platform, post_type, caption, and scheduled_at if missing. Instagra... 2/5 The Vugola MCP server exposes 8 tools across 4 categories: Read, Write, Destructive, Execute.
Use Intercept, the open-source MCP proxy. Write YAML rules for each tool — rate limits, argument validation, or deny rules — then run Intercept in front of the Vugola server.
Vugola tools are categorised as Read (4), Write (2), Destructive (1), Execute (1). Each category has a recommended default policy.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept