This record as markdown: /tools/34892002-bilibili-mcp-js/bilibili-hot.md
What bilibili-hot does on Bilibili MCP Server
AI agents call bilibili-hot to retrieve information from Bilibili MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why bilibili-hot is rated Low
The tool retrieves trending content information from Bilibili's platform. This is a read-only operation that has no side effects, matches the 'list/fetch' pattern of Read category tools, and poses minimal security risk as it only accesses publicly available trending data.
From the tool's definition Tool name 'bilibili-hot' with description '获取B站热门内容' (retrieve Bilibili hot/trending content). This is a retrieval operation that queries and returns trending content data without modifying, executing, or deleting anything.
Attacks that exploit this kind of access
The rule that runs bilibili-hot safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Bilibili MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For bilibili-hot, this is the rule to start with:
bilibili-hot is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Bilibili MCP Server, apply this rule, and every bilibili-hot call is checked against it from then on.
Questions about bilibili-hot
获取B站热门内容. It is categorised as a Read tool in the Bilibili MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Bilibili MCP Server MCP server in PolicyLayer and add a rule for bilibili-hot: 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 MCP Server. Nothing to install.
bilibili-hot 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 bilibili-hot 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 bilibili-hot. 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.
bilibili-hot is provided by the Bilibili MCP Server MCP server (34892002/bilibili-mcp-js). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Bilibili MCP Server, and thousands of servers like it.
This server
Across the catalogue