AI agents use feishu_send_message to create or update resources in Lark Cli — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Lark Cli environment.
This tool sends messages on behalf of the user to groups or individuals. While messages can technically be deleted later, the primary action is to create and deliver content. This is a Write operation because it creates new data (messages) with side effects (recipient notification, message history).
From the tool's definition Tool name 'feishu_send_message' and description '以用户身份发送飞书/Lark 消息到群聊或个人(支持纯文本与 Markdown)' (send Feishu/Lark messages to group chats or individuals as the user's own identity) indicates the tool creates new messages irreversibly.
Attacks that exploit this kind of access
以用户身份发送飞书/Lark 消息到群聊或个人(支持纯文本与 Markdown). It is categorised as a Write tool in the Lark Cli MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Lark Cli MCP server in PolicyLayer and add a rule for feishu_send_message: 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 Lark Cli. Nothing to install.
feishu_send_message is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the feishu_send_message 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.
Set action: deny in the PolicyLayer policy for feishu_send_message. 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.
feishu_send_message is provided by the Lark Cli MCP server (yoreland/lark-cli-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →