AI agents call jellyfin.library_search to retrieve information from Arr Stack without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Search and query operations are Read category tools—they retrieve or query data without modification. The Jellyfin context (media library server) supports this interpretation. Confidence is slightly reduced due to missing description, but the naming convention and sibling tool patterns provide strong contextual evidence that this is a read-only query operation.
From the tool's definition Tool name 'jellyfin.library_search' indicates a search operation. Sibling tools like 'jellyfin.recent_additions', 'jellyfin.scan_library', and 'jellyfin.users_list' are all retrieval/query operations typical of media server APIs.
Attacks that exploit this kind of access
jellyfin.library_search. It is categorised as a Read tool in the Arr Stack MCP Server, which means it retrieves data without modifying state.
Register the Arr Stack MCP server in PolicyLayer and add a rule for jellyfin.library_search: 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 Arr Stack. Nothing to install.
jellyfin.library_search 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 jellyfin.library_search 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 jellyfin.library_search. 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.
jellyfin.library_search is provided by the Arr Stack MCP server (new-usemame/arr-stack-mcp). 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 →