get_msg

Get message details

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-msg.md

WHAT IT DOES

What get_msg does on NapCat MCP Server

AI agents call get_msg 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_msg is rated Low

This tool retrieves message information from the QQ bot system. It performs a read-only query operation that fetches existing data without creating, modifying, deleting, or executing any operations. The classification as 'Read' is appropriate because the tool simply retrieves message details.

From the tool's definition Tool name 'get_msg' with description 'Get message details' indicates retrieval of existing message data without modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_msg 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_msg, this is the rule to start with:

get_msg Allowed

get_msg 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_msg": {}
  }
}

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_msg call is checked against it from then on.

FAQ

Questions about get_msg

What does the get_msg tool do? +

Get message details. 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_msg? +

Register the NapCat MCP Server MCP server in PolicyLayer and add a rule for get_msg: 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_msg? +

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

Can I rate-limit get_msg? +

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

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

get_msg 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 →