AI agents use send_image to create or update resources in Amadeus-QQ-MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Amadeus-QQ-MCP environment.
send_image creates and transmits image data to QQ chats (private or group), modifying chat history and state reversibly. This is a Write operation—data is created/transmitted but not destructively removed or executed as code. Severity is medium because an AI agent sending unexpected images could spam, harass, or violate social trust, but images cannot directly cause financial loss or system compromise.
From the tool's definition Tool name 'send_image' on a QQ messaging server (Amadeus-QQ-MCP) that enables sending messages. Sibling tools include 'send_message' and 'send_voice', establishing a pattern of message-sending operations.
Documented attack patterns abuse exactly the kind of access send_image gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Amadeus-QQ-MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for send_image:
{
"version": "1",
"default": "deny",
"tools": {
"send_image": {
"limits": [
{
"counter": "send_image_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}send_image stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
send_image. It is categorised as a Write tool in the Amadeus-QQ-MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Amadeus-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 Amadeus-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 Amadeus-QQ- MCP server (julesliu390/amadeus-qq-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Amadeus-QQ-MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
10 Amadeus-QQ-MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.