delete_msg

Recall message

SERVERNapCat MCP Server SOURCE1021143806/napcat_mcp

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/1021143806-napcat-mcp/delete-msg.md

WHAT IT DOES

What delete_msg does on NapCat MCP Server

AI agents call delete_msg to permanently remove resources in NapCat MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why delete_msg is rated Critical

Message deletion/recall is an irreversible operation that cannot be undone. Once a message is recalled, it is permanently removed from the conversation history for all participants. This fits the Destructive category as it removes data that cannot be recovered.

From the tool's definition Tool name 'delete_msg' with description 'Recall message' indicates irreversible deletion of messages. Combined with sibling tools like 'delete_essence_msg' and 'delete_group_file' on a QQ bot management server, this confirms destructive message removal…

Attacks that exploit this kind of access

RECOMMENDED RULE

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

delete_msg Hidden

delete_msg is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_msg"
  ]
}

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

FAQ

Questions about delete_msg

What does the delete_msg tool do? +

Recall message. It is categorised as a Destructive tool in the NapCat MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on delete_msg? +

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

delete_msg is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete_msg? +

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

Set action: deny in the PolicyLayer policy for delete_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 delete_msg? +

delete_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 → Critical-risk tools on this server →

Across the catalogue

sms_delete_message on Twilio SMS MCP Server →delete_snapshot on Why Did You Render →calendar_delete_event on Templonix Lite MCP Server →delete_addon_domain on cPanel MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →