This record as markdown: /tools/creativelead-unclick/tmdb-upcoming.md
What tmdb_upcoming does on UnClick
AI agents call tmdb_upcoming 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 |
|---|---|---|---|
page | number | — | |
api_key | string | — |
Parameters from the server's own tool schema.
Why tmdb_upcoming is rated Low
This tool retrieves or queries data (upcoming movies) from an external service without creating, modifying, deleting, or executing any operations. It is a straightforward read-only operation with minimal security risk.
From the tool's definition Tool name 'tmdb_upcoming' and description 'Get upcoming movies from TMDB' indicate a retrieval operation that queries The Movie Database for publicly available upcoming movie information with no data modification or side effects.
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
The rule that runs tmdb_upcoming 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_upcoming, this is the rule to start with:
tmdb_upcoming 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_upcoming call is checked against it from then on.
Questions about tmdb_upcoming
Get upcoming movies from TMDB. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
tmdb_upcoming accepts 2 parameters: page, api_key. 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_upcoming: 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_upcoming 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_upcoming 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_upcoming. 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_upcoming 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