Return the current wake configuration (window title patterns, shortcut).
AI agents call get_wake_config 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.
This tool retrieves and returns existing configuration settings. It performs no mutations, does not execute code or commands, does not delete data, and does not incur financial transactions. The action is purely informational—querying the current state of the wake configuration for inspection purposes.
From the tool's definition Tool name 'get_wake_config' and description 'Return the current wake configuration (window title patterns, shortcut)' indicate a read-only retrieval of configuration data with no modification or side effects.
Attacks that exploit this kind of access
Return the current wake configuration (window title patterns, shortcut). 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 get_wake_config: 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.
get_wake_config 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_wake_config 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_wake_config. 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_wake_config 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 →