risk-scan

name	risk-scan
description	Fast risk-record screen for one company or a batch — 失信被执行, 终本案件, 限制高消费, 司法涉诉, 行政处罚, 股权质押与冻结, 对外担保, 破产重整与司法拍卖, plus adverse media — with severity ranking. Triggers on "风险排查", "有没有失信", "涉诉情况", "被限高了吗", "有没有破产重整", "黑名单筛查", "risk screen", "批量排查供应商".

Company Risk Scan

The fast screen: disclosed risk records + adverse media, ranked. Use standalone or as Step 5 of dd-report.

Workflow

Step 1: Scope

One company or a batch list. For batches, run identical checks per company and output one ranked table; note that depth per name is shallower than a full DD. Each name is its own subject on 天眼查 — anchor and pull a capability list per company, and never carry one company's capability list over to the next.

Step 2: Record checks (per company)

Query in this order, recording per check exactly one of 有记录 / 检索范围内未发现 / 源不可用, plus the source and 检索于 date. These rows become the coverage table in Step 4. A retrieved record is [披露]; a ratio you computed from one (质押比例、担保/净资产) is [测算].

天眼查 reaches these records through a capability list, not by calling a tool name directly. Once per subject: search_companies → get_company_capabilities (with that company_id) → then call_tool per check below, copying tool_name verbatim from the list and passing company_name as the subject. Take company_id from the candidate table's 企业ID column, not from the widest number in the row — the 统一社会信用代码 is longer and ids are not a fixed width, so picking by length lands on the wrong entity. List tools need explicit page/page_size. call_tools_batch takes at most 3 independent checks — use it for plain list pulls that stand alone (2, 3 and 5, or 6's pledge tool and 7), never for a drill-down the vendor marks 建议单独调用 ( under 4, under 6) and never for the exploratory anchoring calls.