screenshot_chat
AI agents call screenshot_chat to retrieve information from Xadeus-QQ-MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The name and server context indicate this tool retrieves or captures chat message content as screenshots, which is a read operation with no side effects on the underlying data. The empty description lowers confidence slightly, but the name combined with the messaging-focused server purpose strongly suggests a read/capture operation rather than modification, deletion, or execution.
From the tool's definition Tool name 'screenshot_chat' and server context involving QQ (messaging platform) with message send/receive and group management capabilities suggests capturing a visual record of chat content.
Attacks that exploit this kind of access
screenshot_chat. It is categorised as a Read tool in the Xadeus-QQ-MCP MCP Server, which means it retrieves data without modifying state.
Register the Xadeus-QQ- MCP server in PolicyLayer and add a rule for screenshot_chat: 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 Xadeus-QQ-MCP. Nothing to install.
screenshot_chat 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 screenshot_chat 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 screenshot_chat. 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.
screenshot_chat is provided by the Xadeus-QQ- MCP server (mouse114514/xadeus-qq-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 →