delete_essence_msg

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

What delete_essence_msg does on NapCat MCP Server

AI agents call delete_essence_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.

Why delete_essence_msg is rated Critical

This tool irreversibly removes data (essence-marked messages) from a group, which cannot be undone. Deletion is the hallmark of the Destructive category. While the blast radius is confined to group communication rather than financial or system-level impact, unauthorized deletion of important group messages constitutes high-severity data loss.

From the tool's definition Tool name 'delete_essence_msg' explicitly uses 'delete' verb paired with 'essence message' — a permanent removal operation. Essence messages are curated important messages in QQ groups that cannot be recovered once deleted.

Questions about delete_essence_msg

What does the delete_essence_msg tool do? +

Delete essence 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_essence_msg? +

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

delete_essence_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_essence_msg? +

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

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

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

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

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of NapCat MCP Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.