This record as markdown: /tools/creativelead-unclick/omdb-search.md
What omdb_search does on UnClick
AI agents call omdb_search to retrieve information from UnClick without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
s | string | — | Search term |
y | number | — | |
type | string | — | |
api_key | string | — |
Parameters from the server's own tool schema.
Why omdb_search is rated Low
This is a straightforward data retrieval tool that queries a movie/TV database and returns search results. It has no capability to modify data, execute code, delete records, or perform financial transactions. The blast radius of misuse is minimal—an agent could only retrieve unwanted information or perform excessive queries, neither of which causes lasting harm. This clearly falls under the Read category.
From the tool's definition Tool performs search operation on OMDB (Open Movie Database) for movies/TV shows. The description uses 'Search' which indicates querying/retrieval without modification or execution of external effects.
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
The rule that runs omdb_search safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For omdb_search, this is the rule to start with:
omdb_search is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect UnClick, apply this rule, and every omdb_search call is checked against it from then on.
Questions about omdb_search
Search movies/TV shows on OMDB. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
omdb_search accepts 4 parameters: s, y, type, api_key. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for omdb_search: 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 UnClick. Nothing to install.
omdb_search 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 omdb_search 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 omdb_search. 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.
omdb_search is provided by the UnClick MCP server (creativelead/unclick). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue