# browse_movies

Browse Blu-ray movies filtered by release year (exact or range) and/or genre. At least one filter is required.

Agent View of the PolicyLayer registry record for `browse_movies`. HTML page: https://policylayer.com/tools/de-bluraysuchmaschine-suche/browse-movies

## Facts

- Tool: `browse_movies`
- Server: Suche (`https://mcp.bluraysuchmaschine.de/mcp`) — https://policylayer.com/tools/de-bluraysuchmaschine-suche.md
- Homepage: https://github.com/https://mcp.bluraysuchmaschine.de/mcp
- Risk category: Read (Low risk)
- Registry record: grade C, identity unverified
- Server auth posture: open
- Server CORS policy: *
- Server rate-limited: no
- Parameters: 5
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `year` | integer | no | Exact release year (e.g. 1999) |
| `genre` | string | no | Genre to filter by (e.g. 'Science Fiction', 'Action') |
| `limit` | integer | no | Maximum number of results (1-25, default 10) |
| `yearTo` | integer | no | End of release year range (inclusive) |
| `yearFrom` | integer | no | Start of release year range (inclusive) |

Parameters from the server's own tool schema.

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "browse_movies",
    "arguments": {}
  }
}
```

## 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 own 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."

## Use case

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.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Suche:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "browse_movies": {}
  }
}
```

## Other tools on Suche (6)

- `browse_by_tag` — Read — https://policylayer.com/tools/de-bluraysuchmaschine-suche/browse-by-tag.md
- `get_featured_movies` — Read — https://policylayer.com/tools/de-bluraysuchmaschine-suche/get-featured-movies.md
- `get_movie_details` — Read — https://policylayer.com/tools/de-bluraysuchmaschine-suche/get-movie-details.md
- `get_similar_movies` — Read — https://policylayer.com/tools/de-bluraysuchmaschine-suche/get-similar-movies.md
- `list_tags` — Read — https://policylayer.com/tools/de-bluraysuchmaschine-suche/list-tags.md
- `search_movies` — Read — https://policylayer.com/tools/de-bluraysuchmaschine-suche/search-movies.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=de-bluraysuchmaschine-suche · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/de-bluraysuchmaschine-suche