AI agents call delete_bitable_records to permanently remove resources in Personal Knowledge MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently deletes records from a data store (Feishu Bitable/multidimensional tables). Deletion is irreversible and cannot be undone. The batch capability amplifies risk by allowing deletion of multiple records in a single call. An AI agent with misuse or prompt injection could delete large amounts of data from the knowledge base or enterprise system.
From the tool's definition Tool name 'delete_bitable_records' and description '删除飞书多维表格记录（支持批量删除）' [Delete Feishu multidimensional table records (supports batch deletion)] — explicit deletion operation with batch capability.
Documented attack patterns abuse exactly the kind of access delete_bitable_records gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Personal Knowledge MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_bitable_records:
{
"version": "1",
"default": "deny",
"hide": [
"delete_bitable_records"
]
}delete_bitable_records 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.
删除飞书多维表格记录（支持批量删除）. It is categorised as a Destructive tool in the Personal Knowledge MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Personal Knowledge MCP Server MCP server in PolicyLayer and add a rule for delete_bitable_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 Personal Knowledge MCP Server. Nothing to install.
delete_bitable_records 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_bitable_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 delete_bitable_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.
delete_bitable_records is provided by the Personal Knowledge MCP Server MCP server (kyodule/personal-knowledge-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Personal Knowledge 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.
29 Personal Knowledge MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.