tmdb.movies.trending

Get trending movies, TV shows, or people — daily or weekly (TMDB)

SERVERApibase SOURCEapibase-mcp-client

Low RISK CLASS

Category Read

Parameters 40 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-whiteknightonhorse-apibase/tmdb.movies.trending.md

WHAT IT DOES

What tmdb.movies.trending does on Apibase

AI agents call tmdb.movies.trending 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: "movie", "tv", "person", or "all" (default "movie")
`window`	string	—	Time window: "day" or "week" (default "week")
`language`	string	—	ISO 639-1 language code (e.g. "en-US"). Default: en-US

Parameters from the server's own tool schema.

RISK

Why tmdb.movies.trending is rated Low

Retrieves public entertainment data without side effects or modification.

From the tool's definition Get trending movies, TV shows, or people

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs tmdb.movies.trending 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.trending, this is the rule to start with:

tmdb.movies.trending Allowed

tmdb.movies.trending is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "tmdb.movies.trending": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Apibase, apply this rule, and every tmdb.movies.trending call is checked against it from then on.

FAQ

Questions about tmdb.movies.trending

What does the tmdb.movies.trending tool do? +

Get trending movies, TV shows, or people — daily or weekly (TMDB). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.

What parameters does tmdb.movies.trending accept? +

tmdb.movies.trending accepts 4 parameters: page, type, window, language. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on tmdb.movies.trending? +

Register the Apibase MCP server in PolicyLayer and add a rule for tmdb.movies.trending: 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.

What risk level is tmdb.movies.trending? +

tmdb.movies.trending is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit tmdb.movies.trending? +

Yes. Add a rate_limit block to the tmdb.movies.trending 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.

How do I block tmdb.movies.trending completely? +

Set action: deny in the PolicyLayer policy for tmdb.movies.trending. 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.

What MCP server provides tmdb.movies.trending? +

tmdb.movies.trending 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.

KEEP EXPLORING

More on Apibase, and thousands of servers like it.

This server

All 1384 Apibase tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →