AI agents invoke play_bilibili_video to trigger actions in xigua-MCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool performs browser automation actions (search, navigate, play video, fullscreen) on an external platform. It executes operations with external side effects and keeps the browser open afterward. It falls under Execute as it triggers external browser operations whose effects depend on the arguments provided.
From the tool's definition 在B站搜索并尝试全屏播放视频(成功后浏览器保持打开)— triggers external browser operations to search and play video on Bilibili in fullscreen
Attacks that exploit this kind of access
在B站搜索并尝试全屏播放视频(成功后浏览器保持打开). It is categorised as a Execute tool in the xigua-MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the xigua- MCP server in PolicyLayer and add a rule for play_bilibili_video: 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 xigua-MCP. Nothing to install.
play_bilibili_video is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the play_bilibili_video 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 play_bilibili_video. 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.
play_bilibili_video is provided by the xigua- MCP server (xiguaxiaome/xigua-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 →