AI agents call get_recent_context to retrieve information from Amadeus-QQ-MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves historical QQ message context without modifying or deleting data. This is a Read operation. Severity is medium rather than low because access to message history could expose sensitive personal communications, financial information, or private conversations if misused by an AI agent without proper authorization checks.
From the tool's definition Tool name 'get_recent_context' indicates retrieval of message history/conversation context. Sibling tools include send_message, send_image, send_voice which are write/execute operations, and batch_get_recent_context which confirms this is a data retrieval…
Documented attack patterns abuse exactly the kind of access get_recent_context 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 get_recent_context:
{
"version": "1",
"default": "deny",
"tools": {
"get_recent_context": {}
}
}get_recent_context is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
get_recent_context. It is categorised as a Read tool in the Amadeus-QQ-MCP MCP Server, which means it retrieves data without modifying state.
Register the Amadeus-QQ- MCP server in PolicyLayer and add a rule for get_recent_context: 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.
get_recent_context is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_recent_context 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 get_recent_context. 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.
get_recent_context 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.