AI agents call list_calendar_events to retrieve information from Feishu without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves calendar events from Feishu without creating, modifying, or deleting data. It is a read-only operation consistent with other retrieval tools on the server like get_doc_content, list_sheets, and list_chat_messages. Misuse would have minimal blast radius as it only exposes existing calendar information visible to the authenticated user.
From the tool's definition Tool name 'list_calendar_events' and description '获取飞书日历的日程列表' (retrieve Feishu calendar event list) indicate data retrieval with no modification or side effects.
Attacks that exploit this kind of access
获取飞书日历的日程列表. It is categorised as a Read tool in the Feishu MCP Server, which means it retrieves data without modifying state.
Register the Feishu MCP server in PolicyLayer and add a rule for list_calendar_events: 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.
list_calendar_events 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 list_calendar_events 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 list_calendar_events. 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.
list_calendar_events is provided by the Feishu MCP server (lm203688/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 →