Get active Jellyfin sessions with current playback information
AI agents call crow_jellyfin_now_playing to retrieve information from Crow without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves current playback state information from Jellyfin (a media server). It performs no modifications to data, executes no code, and has no destructive or financial implications. The blast radius of misuse is minimal—an attacker could learn what media is currently playing but cannot modify, delete, or execute arbitrary actions. It is a straightforward data retrieval operation.
From the tool's definition The tool description states 'Get active Jellyfin sessions with current playback information', which is a retrieval operation with no modification or execution capability. The verb 'Get' explicitly indicates a read-only action.
Documented attack patterns abuse exactly the kind of access crow_jellyfin_now_playing gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Crow, and nothing reaches the server without passing your rules. This is the rule we recommend for crow_jellyfin_now_playing:
{
"version": "1",
"default": "deny",
"tools": {
"crow_jellyfin_now_playing": {}
}
} crow_jellyfin_now_playing is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get active Jellyfin sessions with current playback information. It is categorised as a Read tool in the Crow MCP Server, which means it retrieves data without modifying state.
Register the Crow MCP server in PolicyLayer and add a rule for crow_jellyfin_now_playing: 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 Crow. Nothing to install.
crow_jellyfin_now_playing 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 crow_jellyfin_now_playing 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 crow_jellyfin_now_playing. 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.
crow_jellyfin_now_playing is provided by the Crow MCP server (kh0pper/crow). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Crow, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
576 Crow tools catalogued and risk-classified — across an index of 43,000+ MCP servers.