Get subtitles from a Bilibili video
AI agents call get_subtitles to retrieve information from Bilibili Video Info MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves subtitle data from Bilibili videos without creating, modifying, deleting, or executing any operations. It has no side effects and poses minimal risk even if misused by an AI agent—the worst outcome would be accessing subtitles the agent shouldn't have permission for, which is an authorization concern rather than a tool capability risk.
From the tool's definition Tool name 'get_subtitles' and description 'Get subtitles from a Bilibili video' indicate data retrieval with no modification. Sibling tools 'get_comments' and 'get_danmaku' further confirm this is a read-only data retrieval server.
Attacks that exploit this kind of access
Get subtitles from a Bilibili video. It is categorised as a Read tool in the Bilibili Video Info MCP MCP Server, which means it retrieves data without modifying state.
Register the Bilibili Video Info MCP server in PolicyLayer and add a rule for get_subtitles: 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 Bilibili Video Info MCP. Nothing to install.
get_subtitles 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 get_subtitles 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 get_subtitles. 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.
get_subtitles is provided by the Bilibili Video Info MCP server (masx200/bilibili-video-info-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 →