Get movie cast and crew by ID
AI agents call movie_credits to retrieve information from TMDB MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves publicly available movie credits information from TMDB API. It is a read-only operation with no side effects, no code execution, and no data modification. The retrieval of cast and crew details poses no security risk to the system or user data. Low severity due to the informational nature of the data returned and the absence of any capability to affect system state or user assets.
From the tool's definition Tool name 'movie_credits' and description 'Get movie cast and crew by ID' indicate data retrieval. The operation queries and returns cast and crew information for a movie without modifying, deleting, or executing any operations.
Attacks that exploit this kind of access
Get movie cast and crew by ID. It is categorised as a Read tool in the TMDB MCP Server MCP Server, which means it retrieves data without modifying state.
Register the TMDB MCP Server MCP server in PolicyLayer and add a rule for movie_credits: 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 MCP Server. Nothing to install.
movie_credits 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 movie_credits 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 movie_credits. 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.
movie_credits is provided by the TMDB MCP Server MCP server (ryanxili/tmdb-mcp). 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 →