browse_movies
Browse Blu-ray movies filtered by release year (exact or range) and/or genre. At least one filter is required.
This record as markdown: /tools/de-bluraysuchmaschine-suche/browse-movies.md
What browse_movies does on Suche
AI agents call browse_movies to retrieve information from Suche 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 |
|---|---|---|---|
year | integer | — | Exact release year (e.g. 1999) |
genre | string | — | Genre to filter by (e.g. 'Science Fiction', 'Action') |
limit | integer | — | Maximum number of results (1-25, default 10) |
yearTo | integer | — | End of release year range (inclusive) |
yearFrom | integer | — | Start of release year range (inclusive) |
Parameters from the server's own tool schema.
Why browse_movies is rated Low
This tool queries and retrieves movie data based on user-supplied filters (release year and genre). It has no side effects—it only returns information about existing movies. This is a pure read operation with negligible risk if misused by an AI agent, as it cannot modify data, execute code, or cause harm beyond potentially excessive API calls.
From the tool's definition Tool name 'browse_movies' and description 'Browse Blu-ray movies filtered by...' indicates data retrieval with filtering parameters. No modification, deletion, execution, or financial operations are possible.
Attacks that exploit this kind of access
The rule that runs browse_movies safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Suche, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For browse_movies, this is the rule to start with:
browse_movies 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 Suche, apply this rule, and every browse_movies call is checked against it from then on.
Questions about browse_movies
Browse Blu-ray movies filtered by release year (exact or range) and/or genre. At least one filter is required. It is categorised as a Read tool in the Suche MCP Server, which means it retrieves data without modifying state.
browse_movies accepts 5 parameters: year, genre, limit, yearTo, yearFrom. The full parameter table on this page comes from the server's own tool schema.
Register the Suche MCP server in PolicyLayer and add a rule for browse_movies: 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 Suche. Nothing to install.
browse_movies 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 browse_movies 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 browse_movies. 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.
browse_movies is provided by the Suche MCP server (https://mcp.bluraysuchmaschine.de/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Suche, and thousands of servers like it.
This server
Across the catalogue