This record as markdown: /tools/creativelead-unclick/omdb-by-title.md
What omdb_by_title does on UnClick
AI agents call omdb_by_title 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 |
|---|---|---|---|
t | string | — | |
y | number | — | |
type | string | — | |
api_key | string | — |
Parameters from the server's own tool schema.
Why omdb_by_title is rated Low
This tool retrieves movie or show information from the OMDB (Open Movie Database) based on a title search. It performs a data query operation without creating, modifying, deleting, or executing any external actions. The blast radius is minimal—misuse would only result in excessive queries or information retrieval, not data modification or unauthorized actions.
From the tool's definition Tool name 'omdb_by_title' and description 'Get an OMDB movie/show by title' indicates a query/retrieval operation. The verb 'Get' and the function of retrieving movie/show data by title are read-only operations with no side effects.
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
The rule that runs omdb_by_title 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_by_title, this is the rule to start with:
omdb_by_title 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_by_title call is checked against it from then on.
Questions about omdb_by_title
Get an OMDB movie/show by title. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
omdb_by_title accepts 4 parameters: t, 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_by_title: 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_by_title 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_by_title 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_by_title. 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_by_title 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