tmdb.movies.discover
Discover movies or TV shows by genre, year, rating, language, and sort order (TMDB)
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/tmdb.movies.discover.md
What tmdb.movies.discover does on Apibase
AI agents call tmdb.movies.discover to retrieve information from Apibase 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 |
|---|---|---|---|
page | integer | — | Page number (1-500, default 1) |
type | string | — | Content type to discover: "movie" or "tv" (default "movie") |
year | integer | — | Filter by release year (movies only) |
region | string | — | ISO 3166-1 region for release dates (e.g. "US", "GB") |
sort_by | string | — | Sort field (e.g. "popularity.desc", "vote_average.desc", "revenue.desc", "primary_release_date.desc") |
language | string | — | ISO 639-1 language code (e.g. "en-US"). Default: en-US |
with_genres | string | — | Comma-separated genre IDs to filter (e.g. "28,12" for Action+Adventure) |
include_adult | boolean | — | Include adult content (default false) |
vote_average_gte | number | — | Minimum vote average (0-10) |
vote_average_lte | number | — | Maximum vote average (0-10) |
first_air_date_year | integer | — | Filter by first air date year (TV only) |
primary_release_year | integer | — | Filter by primary release year (movies only) |
Parameters from the server's own tool schema.
Why tmdb.movies.discover is rated Low
Tool queries movie/TV metadata without modifying data or executing operations.
From the tool's definition Discover movies or TV shows by genre, year, rating, language, sort order
Risk signalsHigh parameter count (13 properties)
Attacks that exploit this kind of access
The rule that runs tmdb.movies.discover safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For tmdb.movies.discover, this is the rule to start with:
tmdb.movies.discover 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 Apibase, apply this rule, and every tmdb.movies.discover call is checked against it from then on.
Questions about tmdb.movies.discover
Discover movies or TV shows by genre, year, rating, language, and sort order (TMDB). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
tmdb.movies.discover accepts 12 parameters: page, type, year, region, sort_by, language, with_genres, include_adult, vote_average_gte, vote_average_lte, first_air_date_year, primary_release_year. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for tmdb.movies.discover: 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 Apibase. Nothing to install.
tmdb.movies.discover 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 tmdb.movies.discover 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 tmdb.movies.discover. 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.
tmdb.movies.discover is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue