send_image
AI agents use send_image 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 new messages/artifacts (images) in QQ conversations, which is a reversible write operation. Severity is medium because misuse could spam users, leak sensitive images, or harass contacts, but the action itself is not destructive or financial. Confidence is 0.75 rather than higher because the description is empty, requiring inference from tool name and server context.
From the tool's definition Tool name 'send_image' combined with server context describing 'message send/receive' and 'file sharing' capabilities. The tool sends image data to QQ platform, creating/modifying communication state.
Attacks that exploit this kind of access
send_image. 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_image: 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_image 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_image 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_image. 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_image 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 →