get_friend_list

THE RISK

Low Risk

Why get_friend_list needs a policy

This tool retrieves existing data (friend list) without modifying, deleting, or executing any operations. It is a straightforward query operation analogous to a list or fetch action.

From the tool's definition Tool name 'get_friend_list' and description 'Get the list of QQ friends' indicate a retrieval operation with no side effects.

Documented attack patterns abuse exactly the kind of access get_friend_list gives an agent:

POLICY

How to control get_friend_list

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_friend_list:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_friend_list": {}
  }
}

get_friend_list is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register Amadeus-QQ-MCP — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Amadeus-QQ-MCP tools

Write send_image send_image Write send_message send_message Write send_voice send_voice Read batch_get_recent_context batch_get_recent_context Read check_status Check QQ login status and NapCat connection status. Other compress_context compress_context Read get_group_list Get the list of QQ groups the bot has joined. Read get_recent_context get_recent_context

All 10 Amadeus-QQ-MCP tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about get_friend_list

What does the get_friend_list tool do? +

Get the list of QQ friends. It is categorised as a Read tool in the Amadeus-QQ-MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_friend_list? +

Register the Amadeus-QQ- MCP server in PolicyLayer and add a rule for get_friend_list: 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.

What risk level is get_friend_list? +

get_friend_list is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_friend_list? +

Yes. Add a rate_limit block to the get_friend_list 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.

How do I block get_friend_list completely? +

Set action: deny in the PolicyLayer policy for get_friend_list. 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.

What MCP server provides get_friend_list? +

get_friend_list 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.

Enforce policy on every Amadeus-QQ-MCP tool call.

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.

CHECK YOUR STACK →