AI agents invoke close_camera_preview_tool 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 closes a camera preview window, which is an external operation affecting a running process/UI component. It is analogous to other tools on this server like 'close_browser' and 'close_program', which are Execute-category actions that terminate running processes. The effect depends on the current state of the system and triggers an external operation.
From the tool's definition 关闭摄像头实时预览窗口 (Close camera live preview window)
Attacks that exploit this kind of access
关闭摄像头实时预览窗口。. 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 close_camera_preview_tool: 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.
close_camera_preview_tool 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 close_camera_preview_tool 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 close_camera_preview_tool. 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.
close_camera_preview_tool 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 →