This record as markdown: /tools/creativelead-unclick/tmdb-search-movies.md
What tmdb_search_movies does on UnClick
AI agents call tmdb_search_movies 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 | — | |
year | number | — | |
query | string | — | |
api_key | string | — |
Parameters from the server's own tool schema.
Why tmdb_search_movies is rated Low
This tool retrieves movie data from TMDB without creating, modifying, deleting, or executing code. It is a straightforward information lookup with no capability to alter state or trigger external operations. The blast radius of misuse is minimal—an agent could only retrieve unwanted movie information, which poses no security risk.
From the tool's definition Tool performs a search operation on TMDB (The Movie Database) to retrieve movie information. The verb 'search' and the read-only nature of querying a public movie database indicate no data modification, deletion, or external side effects.
Risk signalsAccepts freeform code/query input (query) · Handles credentials or secrets (api_key)
Attacks that exploit this kind of access
The rule that runs tmdb_search_movies 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_search_movies, this is the rule to start with:
tmdb_search_movies 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_search_movies call is checked against it from then on.
Questions about tmdb_search_movies
Search for movies on TMDB. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
tmdb_search_movies accepts 4 parameters: page, year, query, 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_search_movies: 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_search_movies 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_search_movies 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_search_movies. 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_search_movies 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