Search for actors, directors, or other people in the film industry
AI agents call search_person 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 publicly available information from TMDB about people in the film industry. It has no ability to modify, delete, execute code, or trigger external actions. The blast radius of misuse is minimal — an agent could only retrieve more information than intended, which causes no harm to systems or data integrity.
From the tool's definition Tool description states 'Search for actors, directors, or other people in the film industry' — a pure query/retrieval operation with no side effects.
Documented attack patterns abuse exactly the kind of access search_person 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_person:
{
"version": "1",
"default": "deny",
"tools": {
"search_person": {}
}
}search_person 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 actors, directors, or other people in the film industry. 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_person: 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_person 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_person 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_person. 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_person 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.