tvbox_play_media
AI agents invoke tvbox_play_media to trigger actions in MCP Server for Binge-watch. 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.
The name suggests executing a media playback action on an external device (TVBox), which is an external operation trigger. However, the description is empty, reducing confidence. Based on sibling tool 'mitv_play_media' and the server context (Binge-watch/MoonTV/LunaTV), this tool likely initiates media playback — an Execute-level action.
From the tool's definition Tool name 'tvbox_play_media' implies triggering media playback on a TV box device; description is empty and uninformative.
Attacks that exploit this kind of access
tvbox_play_media. It is categorised as a Execute tool in the MCP Server for Binge-watch MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the MCP Server for Binge-watch MCP server in PolicyLayer and add a rule for tvbox_play_media: 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 MCP Server for Binge-watch. Nothing to install.
tvbox_play_media 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 tvbox_play_media 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 tvbox_play_media. 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.
tvbox_play_media is provided by the MCP Server for Binge-watch MCP server (aahl/mcp-vods). 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 →