AI agents call omdb_search to retrieve information from UnClick without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
s | string | Yes | Search term |
y | number | — | |
type | string | — | |
api_key | string | — |
Parameters from the server's own tool schema.
This is a straightforward read operation against the Open Movie Database API. It searches for and retrieves information about movies and TV shows with no side effects, data modification, or external state changes. The low severity reflects minimal risk even if an AI agent misuses it—worst case is retrieving unwanted movie information.
From the tool's definition Tool name 'omdb_search' and description 'Search movies/TV shows on OMDB' indicate a query operation that retrieves movie/TV show data without modifying any state.
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
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. Required: s. 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 (@unclick/mcp-server). 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 →