This record as markdown: /tools/creativelead-unclick/tmdb-trending.md
What tmdb_trending does on UnClick
AI agents call tmdb_trending to retrieve information from UnClick 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 |
|---|---|---|---|
api_key | string | — | |
media_type | string | — | movie, tv, or all |
time_window | string | — | day or week |
Parameters from the server's own tool schema.
Why tmdb_trending is rated Low
This tool queries and retrieves trending entertainment data from TMDB (The Movie Database). It performs a read-only operation with no ability to modify, delete, or execute external actions. The data returned is public information about what movies and TV shows are currently trending. There is no financial impact, no destructive capability, and no code execution involved.
From the tool's definition Tool name 'tmdb_trending' and description 'Get trending movies or TV shows on TMDB' indicates retrieval of publicly available trending data with no modifications or side effects.
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
The rule that runs tmdb_trending safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For tmdb_trending, this is the rule to start with:
tmdb_trending 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 UnClick, apply this rule, and every tmdb_trending call is checked against it from then on.
Questions about tmdb_trending
Get trending movies or TV shows on TMDB. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
tmdb_trending accepts 3 parameters: api_key, media_type, time_window. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for tmdb_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 UnClick. Nothing to install.
tmdb_trending 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_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.
Set action: deny in the PolicyLayer policy for tmdb_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.
tmdb_trending is provided by the UnClick MCP server (creativelead/unclick). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue