Set a member's group nickname (card). Empty string clears it.
AI agents use set_member_card 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 is a Write operation because it creates or modifies data (a member's group nickname) in a reversible manner. The tool can update the card and the change can be undone by setting it again or clearing it. It is not Execute (no code/command execution), not Destructive (fully reversible), not Financial, and not Read (modifies rather than retrieves).
From the tool's definition Tool description states 'Set a member's group nickname (card). Empty string clears it.' This modifies a user-facing attribute (group nickname/card) that can be changed by the tool but is reversible (can be updated or cleared again).
Attacks that exploit this kind of access
Set a member's group nickname (card). Empty string clears it. 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 set_member_card: 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.
set_member_card 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 set_member_card 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 set_member_card. 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.
set_member_card 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 →