AI agents call tmdb_upcoming to retrieve information from UnClick without modifying anything — 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.
This tool queries a movie database (TMDB) to fetch upcoming movie information. It is a read-only operation that retrieves publicly available data without creating, modifying, deleting, or executing any code. There is no financial impact, destructive capability, or command execution involved. The blast radius of misuse is minimal—an agent could only retrieve irrelevant movie data.
From the tool's definition Tool name contains 'upcoming' and description states 'Get upcoming movies from TMDB' — a retrieval operation with no modification or side effects.
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
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 (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →