AI agents use create_doc to create or update resources in Lark — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Lark environment.
Creating a new document is a Write action—it modifies the state of the Feishu workspace by adding new content, but the action is reversible (the document can be deleted). Severity is medium because unauthorized document creation could clutter workspaces, spam collaborative systems, or create misleading information, but the impact is contained to document creation without financial or destructive consequences.
From the tool's definition Tool name 'create_doc' and description 'Create a new Feishu document' explicitly indicates document creation. This is a reversible write operation that generates new data.
Attacks that exploit this kind of access
Create a new Feishu document with optional content in Markdown format. It is categorised as a Write tool in the Lark MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Lark MCP server in PolicyLayer and add a rule for create_doc: 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. Nothing to install.
create_doc 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 create_doc 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 create_doc. 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.
create_doc is provided by the Lark MCP server (lovelts/lark-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 →