crow_jellyfin_control
Remote control a Jellyfin playback session: play/pause, stop, seek, skip, volume
This record as markdown: /tools/kh0pper-crow/crow-jellyfin-control.md
What crow_jellyfin_control does on Crow
AI agents invoke crow_jellyfin_control to trigger actions in Crow. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why crow_jellyfin_control is rated High
This tool triggers external operations on a remote Jellyfin media server — controlling playback state (play, pause, stop, seek, skip, volume). These are real-time external actions that affect a running session. No data is created or deleted, but external system state is actively manipulated, making Execute the most appropriate category. Misuse could disrupt active media sessions for users.
From the tool's definition Remote control a Jellyfin playback session: play/pause, stop, seek, skip, volume
Attacks that exploit this kind of access
The rule that runs crow_jellyfin_control safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Crow, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For crow_jellyfin_control, this is the rule to start with:
crow_jellyfin_control stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Crow, apply this rule, and every crow_jellyfin_control call is checked against it from then on.
Questions about crow_jellyfin_control
Remote control a Jellyfin playback session: play/pause, stop, seek, skip, volume. It is categorised as a Execute tool in the Crow MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Crow MCP server in PolicyLayer and add a rule for crow_jellyfin_control: 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_control is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the crow_jellyfin_control 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_control. 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_control 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.
More on Crow, and thousands of servers like it.
This server
Across the catalogue