# browse_by_tag

Browse Blu-ray movies by category/tag (e.g. "weihnachtsfilme", "action", "klassiker"). Use list_tags to discover available tags.

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

## Facts

- Tool: `browse_by_tag`
- 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 |
| --- | --- | --- | --- |
| `tag` | string | yes | The tag slug (URL-friendly identifier, e.g. 'weihnachtsfilme', 'action') |
| `limit` | integer | no | Maximum number of results (1-25, default 10) |

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_by_tag",
    "arguments": {
      "tag": "<tag>"
    }
  }
}
```

## Why browse_by_tag is rated Low

This tool retrieves and filters existing movie data based on categorical tags. It has no side effects, creates no data, executes no code, and cannot modify or delete anything. It is a straightforward data retrieval operation, making it a Read-category tool with low severity since misuse would only result in accessing movie information without causing harm.

From the tool's own definition: "Tool performs browsing and filtering operations on movie catalogs by tags/categories. Description explicitly states 'Browse' and references discovering available tags, which are read-only query operations with no modification, deletion, or execution…"

## Use case

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

## Other tools on Suche (6)

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