AI agents call search_by_genre 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 data from TMDB without modifying, executing code, deleting, or performing financial transactions. It is a straightforward search/filter operation with no side effects, placing it firmly in the Read category with low severity since misuse would only expose publicly available movie information.
From the tool's definition Tool name is 'search_by_genre' and description states it 'Search for movies by genre' — a query operation that retrieves movie data based on genre filtering.
Documented attack patterns abuse exactly the kind of access search_by_genre 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 search_by_genre:
{
"version": "1",
"default": "deny",
"tools": {
"search_by_genre": {}
}
}search_by_genre 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.
Search for movies by genre. 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 search_by_genre: 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.
search_by_genre 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 search_by_genre 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 search_by_genre. 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.
search_by_genre 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.