获取电影、电视剧、综艺节目、动漫、番剧、短剧等节目的详情及播放地址
AI agents call vods_detail to retrieve information from MCP Server for Binge-watch without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves details and playback information about video content. The verb '获取' (get/fetch) and the nature of the data (details and playback addresses) confirm this is a read-only operation with no side effects. It queries video content metadata, making it a Read category tool with low severity risk.
From the tool's definition Tool name 'vods_detail' and description '获取电影、电视剧、综艺节目、动漫、番剧、短剧等节目的详情及播放地址' (Get details and playback addresses for movies, TV series, variety shows, anime, etc.) indicate retrieval of metadata and video information without modification or deletion.
Attacks that exploit this kind of access
获取电影、电视剧、综艺节目、动漫、番剧、短剧等节目的详情及播放地址. It is categorised as a Read tool in the MCP Server for Binge-watch MCP Server, which means it retrieves data without modifying state.
Register the MCP Server for Binge-watch MCP server in PolicyLayer and add a rule for vods_detail: 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.
vods_detail 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 vods_detail 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 vods_detail. 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.
vods_detail 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 →