AI agents call get_bitable_records to retrieve information from Personal Knowledge MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves records from a Feishu (enterprise collaboration platform) multidimensional table with optional filtering, field selection, and sorting. These are pure read operations that query and return data without side effects. The presence of sibling tools like 'batch_update_bitable_records', 'create_bitable_records', and 'delete_bitable_records' further confirms this is the read-only variant.
From the tool's definition Tool name 'get_bitable_records' and description '获取飞书多维表格记录，支持筛选、字段选择、排序' (Get Feishu multidimensional table records, supporting filtering, field selection, sorting) indicate a data retrieval operation with no modification or deletion capabilities.
Documented attack patterns abuse exactly the kind of access get_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 get_bitable_records:
{
"version": "1",
"default": "deny",
"tools": {
"get_bitable_records": {}
}
}get_bitable_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.
获取飞书多维表格记录，支持筛选、字段选择、排序. It is categorised as a Read tool in the Personal Knowledge MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Personal Knowledge MCP Server MCP server in PolicyLayer and add a rule for get_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.
get_bitable_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 get_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 get_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.
get_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.