Get movies currently playing in theaters. Returns titles, ratings, release dates, and overviews for movies now in cinemas.
AI agents call get_now_playing 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 queries public movie information from TMDB's current cinema listings. It has no side effects, does not modify data, execute code, delete content, or involve financial transactions. It is a straightforward read operation on a public database.
From the tool's definition Tool description explicitly states it 'Get movies currently playing in theaters' and 'Returns titles, ratings, release dates, and overviews' — purely informational retrieval with no modification, deletion, or execution of external operations.
Documented attack patterns abuse exactly the kind of access get_now_playing 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 get_now_playing:
{
"version": "1",
"default": "deny",
"tools": {
"get_now_playing": {}
}
} get_now_playing 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.
Get movies currently playing in theaters. Returns titles, ratings, release dates, and overviews for movies now in cinemas. 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 get_now_playing: 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.
get_now_playing 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 get_now_playing 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 get_now_playing. 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.
get_now_playing 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.