Find where one or more movie titles are available by searching titles, matching TMDB movies, and checking streaming, rental, and purchase providers
AI agents call find_where_to_watch to retrieve information from Tmdb without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays streaming availability data without creating, modifying, deleting, or executing any operations. It is a read-only query against TMDB and provider databases. While the result may inform purchasing decisions, the tool itself does not process payments or commit financial obligations—that occurs externally through the identified providers.
From the tool's definition Tool description states it 'Find[s] where one or more movie titles are available by searching titles, matching TMDB movies, and checking streaming, rental, and purchase providers' — purely informational retrieval of where content can be watched.
Documented attack patterns abuse exactly the kind of access find_where_to_watch gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Tmdb, and nothing reaches the server without passing your rules. This is the rule we recommend for find_where_to_watch:
{
"version": "1",
"default": "deny",
"tools": {
"find_where_to_watch": {}
}
}find_where_to_watch is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Find where one or more movie titles are available by searching titles, matching TMDB movies, and checking streaming, rental, and purchase providers. It is categorised as a Read tool in the Tmdb MCP Server, which means it retrieves data without modifying state.
Register the Tmdb MCP server in PolicyLayer and add a rule for find_where_to_watch: 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 Tmdb. Nothing to install.
find_where_to_watch 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 find_where_to_watch 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 find_where_to_watch. 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.
find_where_to_watch is provided by the Tmdb MCP server (laksh-star/mcp-server-tmdb). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Tmdb, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
24 Tmdb tools catalogued and risk-classified — across an index of 43,000+ MCP servers.