AI agents call filmography_actor_genre to retrieve information from MCP TMDB without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries filmography data—a read-only operation with no side effects. It searches and returns information about an actor's films filtered by genre. Without evidence of data modification, deletion, or external execution capabilities, it falls under the Read category with low severity since misuse would only expose publicly available film database information.
From the tool's definition Tool name 'filmography_actor_genre' indicates retrieval of actor filmography filtered by genre. No description provided, but the naming pattern matches sibling tools like 'filmography_crew_genre' which query film industry data.
Attacks that exploit this kind of access
filmography_actor_genre. It is categorised as a Read tool in the MCP TMDB MCP Server, which means it retrieves data without modifying state.
Register the MCP TMDB MCP server in PolicyLayer and add a rule for filmography_actor_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 MCP TMDB. Nothing to install.
filmography_actor_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 filmography_actor_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 filmography_actor_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.
filmography_actor_genre is provided by the MCP TMDB MCP server (leonardogilrodriguez/mcp-tmdb). 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 →