# get_similar_movies

Get movies that are similar or related to a specific movie (e.g. same series, same theme).

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

## Facts

- Tool: `get_similar_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 |
| --- | --- | --- | --- |
| `slug` | string | yes | The movie slug (URL-friendly identifier, e.g. 'matrix-1999') |
| `limit` | integer | no | Maximum number of results (1-20, default 8) |

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": "get_similar_movies",
    "arguments": {
      "slug": "<slug>"
    }
  }
}
```

## Why get_similar_movies is rated Low

This tool retrieves and queries movie information based on similarity criteria. It has no capability to create, modify, delete, or execute operations. The action is purely informational, consistent with other Read tools on the server (browse_movies, get_movie_details, search_movies). Low severity reflects minimal risk if misused by an AI agent.

From the tool's own definition: "Tool description states it 'Get movies that are similar or related to a specific movie' — a retrieval operation that queries and returns movie data without modification or side effects."

## Use case

AI agents call get_similar_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": {
    "get_similar_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
- `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