list_videos
List videos from your Zype library with comprehensive filtering. FILTERING STRATEGY - Use precise filters over text search: - For category-based queries (e.g., "SNL videos", "premium content", "action movies"): → Use category filter: {"category": {"YouTube Channel": "Saturday Night Live"}} → Firs...
This record as markdown: /tools/com-zype-mcp-server/list-videos.md
What list_videos does on Zype Com
AI agents call list_videos to retrieve information from Zype Com without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
q | string | — | Search query (searches title, source_id, id, zobject title) |
id | array | — | Filter by specific video IDs (batch lookup) |
page | number | — | Page number (default: 1) |
sort | string | — | Field to sort by (created_at, published_at, title, updated_at) |
order | string | — | Sort order |
active | string | — | Filter by active status |
on_air | boolean | — | Filter by on-air/broadcasting status |
season | number | — | Filter by season number |
country | string | — | Filter by country code |
hulu_id | string | — | Filter by Hulu ID |
keyword | string | — | Filter by keyword/tag |
category | object | — | Filter by category values (e.g., {"Premium": "true", "Genre": "Action"}) |
Parameters from the server's own tool schema.
Why list_videos is rated Low
Even though list_videos only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Risk signalsHigh parameter count (33 properties)
Attacks that exploit this kind of access
The rule that runs list_videos safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Zype Com, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_videos, this is the rule to start with:
list_videos is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Zype Com, apply this rule, and every list_videos call is checked against it from then on.
Questions about list_videos
List videos from your Zype library with comprehensive filtering. FILTERING STRATEGY - Use precise filters over text search: - For category-based queries (e.g., "SNL videos", "premium content", "action movies"): → Use category filter: {"category": {"YouTube Channel": "Saturday Night Live"}} → First call list_categories to see available category names and values - For monetization queries (e.g., "subscription videos", "free content"): → Use monetization filters: subscription_required, pass_required, purchase_required - For series/episodic content: → Use series_id, season, episode filters - For batch operations on known videos: → Use id array filter instead of searching - Use q (text search) only for fuzzy title/description matching when exact filters don't apply Available Filters: - Pagination: page, per_page (max 500) - Text search: q (searches title, source_id, zobject title - use as last resort) - Status: active, on_air, featured, mature_content, friendly_title, keyword - Dates: created_at_gte/lte, published_at_gte/lte, updated_at_gte/lte - Monetization: subscription_required, pass_required, rental_required, purchase_required - Categories: category object (e.g., {"Genre": "Action", "Premium": "true"}) - Series: series_id, season - Source: source_id, dpt_enabled, country - External IDs: youtube_id, vimeo_id, crunchyroll_id, hulu_id - Batch: id (array of video IDs). It is categorised as a Read tool in the Zype Com MCP Server, which means it retrieves data without modifying state.
list_videos accepts 12 parameters: q, id, page, sort, order, active, on_air, season, country, hulu_id, keyword, category. The full parameter table on this page comes from the server's own tool schema.
Register the Zype Com MCP server in PolicyLayer and add a rule for list_videos: 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 Zype Com. Nothing to install.
list_videos is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_videos 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 list_videos. 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.
list_videos is provided by the Zype Com MCP server (zype/zype-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Zype Com, and thousands of servers like it.
This server
Across the catalogue