AI agents call jellyfin.recent_additions 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.
The tool appears to fetch recently added media items from a Jellyfin library—a read-only operation with no side effects. No modification, deletion, or external execution is implied by the name. While the description is empty, the tool name and server context strongly suggest simple data retrieval. Confidence is moderate-to-high due to missing description but consistent naming patterns across related tools.
From the tool's definition Tool name 'jellyfin.recent_additions' indicates a retrieval operation. Context from sibling tools (jellyfin.library_search, jellyfin.now_playing, jellyfin.system_info, jellyfin.users_list) all appear to be Read operations, suggesting this follows the same…
Attacks that exploit this kind of access
jellyfin.recent_additions. 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.recent_additions: 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.recent_additions 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.recent_additions 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.recent_additions. 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.recent_additions 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 →