add_wake_rule
AI agents use add_wake_rule to create or update resources in Xadeus-QQ-MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Xadeus-QQ-MCP environment.
This tool likely creates or modifies automation rules that control when the QQ bot wakes or takes actions. This is reversible (rules can be modified/deleted) and affects system configuration state, placing it in Write category.
From the tool's definition Tool name 'add_wake_rule' suggests adding/modifying a wake rule in an auto-wake system. Description is empty, limiting precision. Sibling tools include 'debug_wake_pipeline' and 'diagnose_wake', confirming this relates to wake/automation configuration.
Attacks that exploit this kind of access
add_wake_rule. It is categorised as a Write tool in the Xadeus-QQ-MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Xadeus-QQ- MCP server in PolicyLayer and add a rule for add_wake_rule: 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.
add_wake_rule is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the add_wake_rule 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 add_wake_rule. 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.
add_wake_rule 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 →