AI agents call bazarr_get_movies_history to retrieve information from Nas without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical records of subtitle downloads from Bazarr, a subtitle management service. It queries existing data without creating, modifying, deleting, or executing external operations. The blast radius of accidental misuse is minimal — worst case, an agent repeatedly calls it and learns what subtitles were previously downloaded, which is informational only.
From the tool's definition Tool name 'bazarr_get_movies_history' and description 'Récupère l'historique des téléchargements de sous-titres pour les films' (Retrieves the history of subtitle downloads for movies) — uses 'get' and 'history', indicating data retrieval with no modification…
Attacks that exploit this kind of access
Récupère l'historique des téléchargements de sous-titres pour les films. It is categorised as a Read tool in the Nas MCP Server, which means it retrieves data without modifying state.
Register the Nas MCP server in PolicyLayer and add a rule for bazarr_get_movies_history: 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 Nas. Nothing to install.
bazarr_get_movies_history 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 bazarr_get_movies_history 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 bazarr_get_movies_history. 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.
bazarr_get_movies_history is provided by the Nas MCP server (matthieurosset/nas-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →