AI agents call list_events to retrieve information from Lark MCP Server 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 event data without creating, modifying, deleting, or executing any operations. It is a straightforward read operation with minimal risk; the worst-case scenario is information disclosure of the user's calendar events.
From the tool's definition Tool name is 'list_events' and description states 'List events from the user on Lark' — a clear retrieval operation with no modification or side effects.
Documented attack patterns abuse exactly the kind of access list_events gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Lark MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for list_events:
{
"version": "1",
"default": "deny",
"tools": {
"list_events": {}
}
}list_events is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List events from the user on Lark. It is categorised as a Read tool in the Lark MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Lark MCP Server MCP server in PolicyLayer and add a rule for list_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 Lark MCP Server. Nothing to install.
list_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_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_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_events is provided by the Lark MCP Server MCP server (junyuan-qi/lark-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Lark MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
5 Lark MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.