AI agents call get_doc_content to retrieve information from Lark without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves document or wiki page content by URL. It performs a query operation with no side effects—no data is created, modified, deleted, or executed. The OAuth-authenticated access ensures proper authorization, but the operation itself is purely informational. Classified as Read with low severity since data retrieval poses minimal risk compared to write, execute, or destructive operations.
From the tool's definition Tool name 'get_doc_content' and description 'Get content of a Feishu document or wiki page by URL' explicitly indicate retrieval of existing data without modification.
Attacks that exploit this kind of access
Get content of a Feishu document or wiki page by URL. It is categorised as a Read tool in the Lark MCP Server, which means it retrieves data without modifying state.
Register the Lark MCP server in PolicyLayer and add a rule for get_doc_content: 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.
get_doc_content 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 get_doc_content 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 get_doc_content. 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.
get_doc_content 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.
get_doc_content is one line of Lark's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →