Low Risk

search_by_keyword

Search for movies by keywords or themes

How to control search_by_keyword ↓

What search_by_keyword does on Tmdb

AI agents call search_by_keyword 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.

Low Risk

Why search_by_keyword needs a policy

This tool retrieves movie data based on search queries without modifying, deleting, or executing any operations. It is a straightforward read operation that queries a database for matching results. No financial transactions, destructive actions, or code execution are involved.

From the tool's definition Tool name 'search_by_keyword' and description 'Search for movies by keywords or themes' indicate a retrieval operation with no side effects. The TMDB API context confirms this is a query-only operation.

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

How to control search_by_keyword

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

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "search_by_keyword": {}
  }
}

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

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

Free to start. No card required.

Related tools and policies

Go deeper

Questions about search_by_keyword

What does the search_by_keyword tool do? +

Search for movies by keywords or themes. 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 search_by_keyword? +

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

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

Can I rate-limit search_by_keyword? +

Yes. Add a rate_limit block to the search_by_keyword 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 search_by_keyword completely? +

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

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

Free to start. No card required.

24 Tmdb tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.