AI agents call get_record 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.
The tool name 'get_record' follows standard read-operation naming patterns. While the description is empty, the server's stated purpose and the presence of clearly destructive siblings (delete_record, delete_field, delete_table) and write siblings (create_record, update_field) establish that 'get_record' belongs in the retrieval category.
From the tool's definition Tool name 'get_record' indicates data retrieval. The server description states it provides 'read and write access' to databases and enables inspection; 'get_record' aligns with the read capability (alongside sibling tools like list_records, list_fields,…
Documented attack patterns abuse exactly the kind of access get_record 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 get_record:
{
"version": "1",
"default": "deny",
"tools": {
"get_record": {}
}
}get_record 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.
get_record. 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 get_record: 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.
get_record 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_record 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_record. 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_record 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.