AI agents call feishu_wiki_node_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.
The tool retrieves and enumerates Wiki nodes, which is a read-only operation. No data is created, modified, deleted, or executed. The blast radius of misuse is minimal—an agent could at worst enumerate Wiki structure it shouldn't access, but cannot alter or execute anything. Assigned low severity because unauthorized enumeration of Wiki content has limited impact compared to write or destructive operations.
From the tool's definition Tool name contains 'list' and description states '列出某个 Wiki 空间或父节点下的节点' (list nodes under a Wiki space or parent node). This is a retrieval operation with no modification or execution of external effects.
Attacks that exploit this kind of access
列出某个 Wiki 空间或父节点下的节点. 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_wiki_node_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_wiki_node_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_wiki_node_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_wiki_node_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_wiki_node_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 →