# bilibili-hot

获取B站热门内容

Agent View of the PolicyLayer registry record for `bilibili-hot`. HTML page: https://policylayer.com/tools/34892002-bilibili-mcp-js/bilibili-hot

## Facts

- Tool: `bilibili-hot`
- Server: Bilibili MCP Server (`34892002/bilibili-mcp-js`) — https://policylayer.com/tools/34892002-bilibili-mcp-js.md
- Homepage: https://github.com/34892002/bilibili-mcp-js
- Risk category: Read (Low risk)
- Registry record: grade B, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Allowed

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "bilibili-hot",
    "arguments": {}
  }
}
```

## 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 own 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."

## Use case

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.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Bilibili MCP Server:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "bilibili-hot": {}
  }
}
```

## Other tools on Bilibili MCP Server (7)

- `bilibili-bangumi-timeline` — Read — https://policylayer.com/tools/34892002-bilibili-mcp-js/bilibili-bangumi-timeline.md
- `bilibili-search-summary` — Read — https://policylayer.com/tools/34892002-bilibili-mcp-js/bilibili-search-summary.md
- `bilibili-user-complete` — Read — https://policylayer.com/tools/34892002-bilibili-mcp-js/bilibili-user-complete.md
- `bilibili-user-info` — Read — https://policylayer.com/tools/34892002-bilibili-mcp-js/bilibili-user-info.md
- `bilibili-user-stat` — Read — https://policylayer.com/tools/34892002-bilibili-mcp-js/bilibili-user-stat.md
- `bilibili-user-videos` — Read — https://policylayer.com/tools/34892002-bilibili-mcp-js/bilibili-user-videos.md
- `bilibili-video-detail` — Read — https://policylayer.com/tools/34892002-bilibili-mcp-js/bilibili-video-detail.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=34892002-bilibili-mcp-js · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/34892002-bilibili-mcp-js