AI agents call feishu_base_table_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 queries and returns a list of tables within a Feishu/Lark Base/Bitable structure. It performs a read-only operation that retrieves metadata about existing tables without creating, modifying, deleting, or executing any side effects. The blast radius is limited to information disclosure of table structures the user already has access to.
From the tool's definition Tool name 'feishu_base_table_list' and description '列出某个多维表格（Bitable/Base）下的所有数据表' (list all data tables in a Bitable/Base) indicate a retrieval operation with no modification or deletion of data.
Attacks that exploit this kind of access
列出某个多维表格（Bitable/Base）下的所有数据表. 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_table_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_table_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_table_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_table_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_table_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 →