# bilibili-user-info

获取UP主基本信息

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

## Facts

- Tool: `bilibili-user-info`
- 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-user-info",
    "arguments": {}
  }
}
```

## Why bilibili-user-info is rated Low

This tool retrieves basic information about content creators (UP主) on Bilibili. No evidence of modification, deletion, execution, or financial operations. It is a simple informational lookup with no side effects, fitting the Read category. Low severity due to limited blast radius from misuse—worst case is unauthorized access to publicly available creator profile data.

From the tool's own definition: "Tool name 'bilibili-user-info' and description '获取UP主基本信息' (Get UP creator basic information) indicate data retrieval only."

## Use case

AI agents call bilibili-user-info 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-user-info": {}
  }
}
```

## Other tools on Bilibili MCP Server (7)

- `bilibili-bangumi-timeline` — Read — https://policylayer.com/tools/34892002-bilibili-mcp-js/bilibili-bangumi-timeline.md
- `bilibili-hot` — Read — https://policylayer.com/tools/34892002-bilibili-mcp-js/bilibili-hot.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-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
