browse_by_tag
Browse Blu-ray movies by category/tag (e.g. "weihnachtsfilme", "action", "klassiker"). Use list_tags to discover available tags.
This record as markdown: /tools/de-bluraysuchmaschine-suche/browse-by-tag.md
What browse_by_tag does on Suche
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.
| Parameter | Type | Required | Description |
|---|---|---|---|
tag | string | Yes | The tag slug (URL-friendly identifier, e.g. 'weihnachtsfilme', 'action') |
limit | integer | — | Maximum number of results (1-25, default 10) |
Parameters from the server's own tool schema.
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 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…
Attacks that exploit this kind of access
The rule that runs browse_by_tag 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_by_tag, this is the rule to start with:
browse_by_tag 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_by_tag call is checked against it from then on.
Questions about browse_by_tag
Browse Blu-ray movies by category/tag (e.g. "weihnachtsfilme", "action", "klassiker"). Use list_tags to discover available tags. It is categorised as a Read tool in the Suche MCP Server, which means it retrieves data without modifying state.
browse_by_tag accepts 2 parameters: tag, limit. Required: tag. 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_by_tag: 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_by_tag 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_by_tag 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_by_tag. 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_by_tag 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