AI agents call delete_field to permanently remove resources in Lark Base MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
delete_field performs irreversible deletion of database schema elements (fields/columns). This cannot be undone and affects all records in that field. Despite the empty description, the tool name unambiguously indicates destructive intent, and context from the server's other destructive tools (delete_record, delete_table) confirms this classification.
From the tool's definition Tool name 'delete_field' explicitly indicates deletion of a database field. The server description confirms write and manipulation capabilities on Feishu Base databases.
Documented attack patterns abuse exactly the kind of access delete_field 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 delete_field:
{
"version": "1",
"default": "deny",
"hide": [
"delete_field"
]
}delete_field disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
delete_field. It is categorised as a Destructive tool in the Lark Base MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Lark Base MCP Server MCP server in PolicyLayer and add a rule for delete_field: 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.
delete_field is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_field 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 delete_field. 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.
delete_field 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.