get_person_details

THE RISK

Low Risk

Why get_person_details needs a policy

This is a straightforward data retrieval operation. It queries an external API (TMDB) for publicly available information about people in the entertainment industry and returns that data. There are no side effects, no data modification, no code execution, and no financial implications. This clearly fits the Read category with low severity.

From the tool's definition Tool is 'Get full biography and filmography for an actor or director' — retrieves biographical and filmography data from TMDB with no modification, deletion, or execution capability.

Documented attack patterns abuse exactly the kind of access get_person_details gives an agent:

POLICY

How to control get_person_details

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 get_person_details:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_person_details": {}
  }
}

get_person_details is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register Tmdb — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Tmdb tools

Read build_collection_gap_plan Build a franchise completion plan by comparing watched titles or TMDB IDs against a collec Read build_franchise_watch_order Build a franchise or universe watch guide with release order, suggested order, total runti Read build_person_watch_path Build a watch path for an actor, director, or crew member with best-rated, available-now, Read build_release_calendar_watchlist Build a release-window watchlist with upcoming movies, provider-ready picks, broad-room ba Read advanced_search Advanced movie search with multiple filters Read compare_movies Compare 2 to 5 movies side by side with ratings, runtime, genres, cast, director, watch pr Read find_where_to_watch Find where one or more movie titles are available by searching titles, matching TMDB movie Read get_movie_details Get full details for a movie including cast, crew, runtime, budget, and reviews

All 24 Tmdb tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about get_person_details

What does the get_person_details tool do? +

Get full biography and filmography for an actor or director. It is categorised as a Read tool in the Tmdb MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_person_details? +

Register the Tmdb MCP server in PolicyLayer and add a rule for get_person_details: 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.

What risk level is get_person_details? +

get_person_details is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_person_details? +

Yes. Add a rate_limit block to the get_person_details 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.

How do I block get_person_details completely? +

Set action: deny in the PolicyLayer policy for get_person_details. 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.

What MCP server provides get_person_details? +

get_person_details 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.

Enforce policy on every Tmdb tool call.

Start from Tmdb, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →