Lark Cli

19 tools. 5 can modify or destroy data without limits.

5 write tools that can modify data. Rate limits recommended.

Last updated:

5 can modify or destroy data
14 read-only
19 tools total

Community server · catalogue entry verified 02/07/2026

How to control Lark Cli ↓

What Lark Cli exposes to your agents

Read (14) Write / Execute (5) Destructive / Financial (0)
High Risk

The most dangerous Lark Cli tools

5 of Lark Cli's 19 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

How to control Lark Cli

PolicyLayer is an MCP gateway — it sits between your AI agents and Lark Cli, and nothing reaches the server without passing your rules. These are the rules we recommend:

Rate limit write operations
{
  "feishu_base_record_upsert": {
    "limits": [
      {
        "counter": "feishu_base_record_upsert_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations
{
  "feishu_base_field_list": {
    "limits": [
      {
        "counter": "feishu_base_field_list_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

  1. Create a free account and register Lark Cli — nothing to install.
  2. Add these rules — paste them, or build them visually. Tune the limits to your setup.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
ENFORCE POLICY ON LARK CLI →

Instant setup, no code required.

All 19 Lark Cli tools

Questions about Lark Cli

How do I prevent bulk modifications through Lark Cli? +

The Lark Cli server has 5 write tools including feishu_base_record_upsert, feishu_doc_create, feishu_doc_update. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Lark Cli.

How many tools does the Lark Cli MCP server expose? +

19 tools across 2 categories: Read, Write. 14 are read-only. 5 can modify, create, or delete data.

How do I enforce a policy on Lark Cli? +

Register the Lark Cli MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Lark Cli tool call.

Deterministic rules across all 19 Lark Cli tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Instant setup, no code required.

19 Lark Cli 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.