AI agents call get_user_info to retrieve information from bilibili MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves publicly available user information from Bilibili without any side effects or data modification. It is a simple query operation that fetches existing data, consistent with the 'Read' category. The severity is low because user information on social platforms is typically public or semi-public, and retrieval alone poses minimal risk unless the user data is sensitive or private.
From the tool's definition Tool name 'get_user_info' and description 'Get information about a Bilibili user' indicate retrieval of user data with no modification capability.
Documented attack patterns abuse exactly the kind of access get_user_info gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and bilibili MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_user_info:
{
"version": "1",
"default": "deny",
"tools": {
"get_user_info": {}
}
}get_user_info is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get information about a Bilibili user. 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 get_user_info: 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.
get_user_info 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_user_info 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_user_info. 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_user_info is provided by the bilibili MCP Server MCP server (wangshunnn/bilibili-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from bilibili MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
3 bilibili MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.