AI agents call list_records to retrieve information from Lark Base MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Despite empty description, the tool name 'list_records' and pattern consistency with other list_* siblings indicate a data retrieval operation with no side effects. This is a query/fetch operation returning records from a database, classified as Read. Severity is low because listing records has minimal blast radius—it exposes data but cannot modify, delete, or execute operations.
From the tool's definition Tool named 'list_records' with sibling tools showing clear CRUD patterns: create_*, delete_*, get_*, update_*, and list_* operations. The 'list_' prefix is a standard read operation pattern.
Documented attack patterns abuse exactly the kind of access list_records gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Lark Base MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for list_records:
{
"version": "1",
"default": "deny",
"tools": {
"list_records": {}
}
}list_records 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_records. It is categorised as a Read tool in the Lark Base MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Lark Base MCP Server MCP server in PolicyLayer and add a rule for list_records: 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 Base MCP Server. Nothing to install.
list_records 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_records 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_records. 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_records is provided by the Lark Base MCP Server MCP server (lark-base-team/lark-base-mcp-node-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Lark Base 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.
13 Lark Base MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.