AI agents call feishu_base_record_list to retrieve information from Lark Cli without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and lists records from a database table with optional filtering and sorting. It performs read-only operations with no side effects. However, severity is elevated to 'medium' rather than 'low' because: (1) the MCP server operates with the user's own identity on Feishu/Lark, a workplace communication/collaboration platform, so retrieved records may contain sensitive workplace data; (2) an AI agent…
From the tool's definition Tool name 'feishu_base_record_list' and description '列出多维表格某个数据表的记录（行），支持筛选/排序' (list records/rows from a multidimensional table, supporting filtering/sorting) indicate data retrieval with no modification or deletion.
Attacks that exploit this kind of access
列出多维表格某个数据表的记录（行），支持筛选/排序. It is categorised as a Read tool in the Lark Cli MCP Server, which means it retrieves data without modifying state.
Register the Lark Cli MCP server in PolicyLayer and add a rule for feishu_base_record_list: 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_base_record_list is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the feishu_base_record_list 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_base_record_list. 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_base_record_list 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 →