# search_movies

Search the Blu-ray movie database by title, director, actor, or keywords.

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

## Facts

- Tool: `search_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: 2 (1 required)
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `limit` | integer | no | Maximum number of results (1-25, default 10) |
| `query` | string | yes | Search query (movie title, director, actor, or keywords) |

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": "search_movies",
    "arguments": {
      "query": "<query>"
    }
  }
}
```

## Why search_movies is rated Low

This tool only retrieves or queries existing movie data from a database. It does not create, modify, delete, or execute any operations — it simply returns search results based on user-supplied criteria. This is a low-severity read operation with minimal risk of misuse.

From the tool's own definition: "Tool description states 'Search the Blu-ray movie database by title, director, actor, or keywords' — this is a search/query operation that retrieves data with no side effects."

## Use case

AI agents call search_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": {
    "search_movies": {}
  }
}
```

## Other tools on Suche (6)

- `browse_by_tag` — Read — https://policylayer.com/tools/de-bluraysuchmaschine-suche/browse-by-tag.md
- `browse_movies` — Read — https://policylayer.com/tools/de-bluraysuchmaschine-suche/browse-movies.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

## 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