send_group_notice
AI agents use send_group_notice 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 creates and distributes a notice to a group, which is a reversible write operation affecting group communication state. It is not destructive (notice can be deleted/replaced), not financial, not execute (does not run arbitrary code), and not read-only. Severity is medium because misuse could spam groups or broadcast unwanted messages, but the impact is limited to one group and reversible.
From the tool's definition Tool name 'send_group_notice' combined with server context describing 'message send/receive, group management'; the verb 'send' indicates creation of a notice that modifies group state. Description is empty, reducing confidence slightly.
Attacks that exploit this kind of access
send_group_notice. 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 send_group_notice: 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.
send_group_notice 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 send_group_notice 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 send_group_notice. 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.
send_group_notice 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 →