AI agents invoke lark_start_monitor to trigger actions in Feishu Enhance. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool starts an active monitoring session on Feishu (Lark), which is an operation that triggers external system behavior and whose effects depend on how the monitoring is configured and used. It is not merely reading data (Read), as it initiates a continuous monitoring process rather than retrieving static information.
From the tool's definition Tool name 'lark_start_monitor' with description '启动飞书消息监控会话' (Start Feishu message monitoring session). The description explicitly indicates this tool initiates/starts a monitoring session, which is an active operation that triggers an external system…
Documented attack patterns abuse exactly the kind of access lark_start_monitor gives an agent:
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_start_monitor:
{
"version": "1",
"default": "deny",
"tools": {
"lark_start_monitor": {
"limits": [
{
"counter": "lark_start_monitor_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}lark_start_monitor stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
启动飞书消息监控会话. It is categorised as a Execute tool in the Feishu Enhance MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Feishu Enhance MCP server in PolicyLayer and add a rule for lark_start_monitor: 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.
lark_start_monitor is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the lark_start_monitor 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 lark_start_monitor. 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.
lark_start_monitor 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.
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.