AI agents use feishu_doc_create 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 creates new documents in Feishu, which is a reversible write operation. It does not delete, execute arbitrary code, move money, or retrieve data. The severity is medium because unauthorized document creation could pollute the workspace, create confusion, or expose sensitive information structures, but the operation itself can be undone by deletion.
From the tool's definition Tool name 'feishu_doc_create' and description stating it creates new Feishu documents (creates new documents, optionally in a specified target folder). This is a create operation that modifies the system state by adding new 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_doc_create: 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_doc_create 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_doc_create 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_doc_create. 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_doc_create 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 →