列出飞书文档中的所有 Block，用于了解文档结构或获取特定 Block ID 进行后续操作。
AI agents call feishu_list_blocks to retrieve information from Feishu MCP Server 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 structural information about document blocks without modifying, deleting, or executing any operations. It is purely informational, used for discovery and understanding document composition. The highest risk would be information disclosure of document structure, which is minimal in a controlled environment.
From the tool's definition Tool name 'feishu_list_blocks' and description '列出飞书文档中的所有 Block，用于了解文档结构或获取特定 Block ID 进行后续操作' (list all blocks in Feishu documents to understand document structure or retrieve specific block IDs for subsequent operations) indicate a query/retrieval…
Attacks that exploit this kind of access
列出飞书文档中的所有 Block，用于了解文档结构或获取特定 Block ID 进行后续操作。. It is categorised as a Read tool in the Feishu MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Feishu MCP Server MCP server in PolicyLayer and add a rule for feishu_list_blocks: 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 MCP Server. Nothing to install.
feishu_list_blocks 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_list_blocks 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_list_blocks. 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_list_blocks is provided by the Feishu MCP Server MCP server (redleaves/feishu-mcp-server). 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 →