LanceDBテーブルの破損を検出し、自動修復します。破損テーブルはdrop→再作成されます。修復後は再インデックス（index rebuild）が必要です。
AI agents call maintenance_repair to permanently remove resources in Search Docs — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Although the tool's purpose is repair (maintenance), the mechanism involves irreversible deletion via DROP and table recreation. This crosses into Destructive territory because data loss is inherent to the operation—tables are dropped, not merely modified. Even if the stated intent is corrective, the actual effect is data deletion that cannot be undone without backups.
From the tool's definition Tool description states 'drop→再作成' (drop and recreate), which irreversibly deletes and recreates LanceDB tables. The phrase indicates the tool drops corrupted tables as part of its repair process.
Attacks that exploit this kind of access
LanceDBテーブルの破損を検出し、自動修復します。破損テーブルはdrop→再作成されます。修復後は再インデックス（index rebuild）が必要です。. It is categorised as a Destructive tool in the Search Docs MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Search Docs MCP server in PolicyLayer and add a rule for maintenance_repair: 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 Search Docs. Nothing to install.
maintenance_repair 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 maintenance_repair 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 maintenance_repair. 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.
maintenance_repair is provided by the Search Docs MCP server (otolab/search-docs). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →