AI agents use feishu_bitable to create or update resources in Feishu — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Feishu environment.
The tool performs reversible data modifications (create and update operations on records in Feishu tables). While it includes read/query capability, the primary capability encompasses creating and modifying data. This is Write-category because modifications are reversible and can be undone through updates or deletions by other tools.
From the tool's definition Tool description states '读写飞书多维表格数据(新增/查询/更新记录)' which translates to 'read/write Feishu multidimensional table data (add/query/update records)'. The '新增' (add) and '更新' (update) components indicate creation and modification of data.
Attacks that exploit this kind of access
读写飞书多维表格数据(新增/查询/更新记录). It is categorised as a Write tool in the Feishu MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Feishu MCP server in PolicyLayer and add a rule for feishu_bitable: 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. Nothing to install.
feishu_bitable is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the feishu_bitable 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_bitable. 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_bitable is provided by the Feishu MCP server (zlplzp123wyt/feishu-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 →