AI agents call two_movies 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.
The tool almost certainly retrieves or queries data about movies (likely finding connections or relationships between two films) from TMDB. The sibling tools are all Read-category queries (searching filmographies, listing jobs, finding actor collaborations). No description is provided, which slightly lowers confidence, but the context strongly indicates this is a retrieval operation with no side effects.
From the tool's definition Tool name 'two_movies' on a TMDB MCP server with sibling tools like 'filmography_actor_genre', 'two_actors_on_screen', and 'two_people' suggests querying film database information.
Attacks that exploit this kind of access
two_movies. 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 two_movies: 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.
two_movies 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 two_movies 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 two_movies. 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.
two_movies 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 →