AI agents invoke lark_enable_schedule_task 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 controls the execution state of scheduled tasks — enabling or disabling them triggers or suppresses future automated operations. This is an Execute-category action because it controls external operational behavior (task scheduling/execution), not merely reading or writing data. Misuse could cause unintended automated actions to run or stop at scale.
From the tool's definition 启用或禁用定时任务 (Enable or disable scheduled tasks)
Documented attack patterns abuse exactly the kind of access lark_enable_schedule_task 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_enable_schedule_task:
{
"version": "1",
"default": "deny",
"tools": {
"lark_enable_schedule_task": {
"limits": [
{
"counter": "lark_enable_schedule_task_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}lark_enable_schedule_task 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_enable_schedule_task: 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_enable_schedule_task 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_enable_schedule_task 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_enable_schedule_task. 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_enable_schedule_task 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.