get_friend_msg_history

Get friend message history

SERVERNapCat MCP Server SOURCE1021143806/napcat_mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/1021143806-napcat-mcp/get-friend-msg-history.md

WHAT IT DOES

What get_friend_msg_history does on NapCat MCP Server

AI agents call get_friend_msg_history to retrieve information from NapCat MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why get_friend_msg_history is rated Low

This is a Read operation—it queries and retrieves friend message history with no side effects. Severity is medium because message history may contain sensitive personal or private communications, creating a moderate risk if an AI agent leaks or misuses retrieved data.

From the tool's definition Tool name is 'get_friend_msg_history' and description states 'Get friend message history'. This retrieves historical message data without modification.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_friend_msg_history safely

PolicyLayer is an MCP gateway: it sits between your AI agents and NapCat MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_friend_msg_history, this is the rule to start with:

get_friend_msg_history Allowed

get_friend_msg_history is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

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

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect NapCat MCP Server, apply this rule, and every get_friend_msg_history call is checked against it from then on.

FAQ

Questions about get_friend_msg_history

What does the get_friend_msg_history tool do? +

Get friend message history. It is categorised as a Read tool in the NapCat MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_friend_msg_history? +

Register the NapCat MCP Server MCP server in PolicyLayer and add a rule for get_friend_msg_history: 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 NapCat MCP Server. Nothing to install.

What risk level is get_friend_msg_history? +

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

Can I rate-limit get_friend_msg_history? +

Yes. Add a rate_limit block to the get_friend_msg_history 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_msg_history completely? +

Set action: deny in the PolicyLayer policy for get_friend_msg_history. 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_msg_history? +

get_friend_msg_history is provided by the NapCat MCP Server MCP server (1021143806/napcat_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on NapCat MCP Server, and thousands of servers like it.

This server

All 57 NapCat MCP Server tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →