Critical Risk →

lark_clear_queue

清空消息队列

How to control lark_clear_queue ↓

What lark_clear_queue does on Feishu Enhance

AI agents call lark_clear_queue to permanently remove resources in Feishu Enhance — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

Why lark_clear_queue needs a policy

Clearing a message queue is a destructive operation that irreversibly removes all pending messages without the ability to recover them. This fits the Destructive category as it erases data.

From the tool's definition Tool name 'lark_clear_queue' combined with description '清空消息队列' (clear message queue) indicates irreversible deletion of queued messages. The description explicitly states clearing/emptying the queue, which cannot be undone.

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

How to control lark_clear_queue

PolicyLayer is an MCP gateway — it sits between your AI agents and Feishu Enhance, and nothing reaches the server without passing your rules. This is the rule we recommend for lark_clear_queue:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "lark_clear_queue"
  ]
}

lark_clear_queue disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register Feishu Enhance — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about lark_clear_queue

What does the lark_clear_queue tool do? +

清空消息队列. It is categorised as a Destructive tool in the Feishu Enhance 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 lark_clear_queue? +

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

What risk level is lark_clear_queue? +

lark_clear_queue 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 lark_clear_queue? +

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

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

lark_clear_queue is provided by the Feishu Enhance MCP server (jiaxinghit/feishu-enhance-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Feishu Enhance tool call.

Start from Feishu Enhance, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

24 Feishu Enhance tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.