获取总部数据指标报表，生成 Excel 文件。支持两种模式： 1. 旧模式（不传 statisticsScope）：固定查询城市公司+营销线层级两个维度，使用默认20项指标 2. 动态模式（传入 statisticsScope）：按指定维度和条件进行单轮查询，支持自定义指标 ⚠️ 动态模式的所有参数值（branchIds、bizlineIds、storeManagerIds、agentCodeQueries 等）必须先通过 statement_query 工具查询获取真实值，严禁自行编造或猜测 ID/code。 调用顺序：statement_query(get_query_guide) ...
Risk signalsHigh parameter count (12 properties)
Part of the Yjzf server.
Free to start. No card required.
AI agents call count_all_statement to retrieve information from Yjzf without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though count_all_statement only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"count_all_statement": {}
}
}See the full Yjzf policy for all 16 tools.
These attack patterns abuse exactly the kind of access count_all_statement gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
获取总部数据指标报表，生成 Excel 文件。支持两种模式： 1. 旧模式（不传 statisticsScope）：固定查询城市公司+营销线层级两个维度，使用默认20项指标 2. 动态模式（传入 statisticsScope）：按指定维度和条件进行单轮查询，支持自定义指标 ⚠️ 动态模式的所有参数值（branchIds、bizlineIds、storeManagerIds、agentCodeQueries 等）必须先通过 statement_query 工具查询获取真实值，严禁自行编造或猜测 ID/code。 调用顺序：statement_query(get_query_guide) → statement_query(get_branches) → [维度专属查询] → statement_query(get_statistics_targets) → 本工具。 用户说某个指标大类名称（如"房源库存指标"）时，必须传入该大类下返回的所有父级 code，不可只传一个。 不传时间参数时默认查询当月第一天到昨天，最大时间间隔 12 个月。不需要自行计算时间戳，不传即可使用默认值。 🔁 后续/重复导出规则：当用户要求"把其他城市也导一份"或"换个城市再导一次"时： - agentCodeQueries 必须与上一次成功导出使用的完全相同（同样的 code 列表、同样的数量） - statisticsScope 必须与上一次相同 - 仅 branchIds、bizlineIds、storeManagerIds 需要根据新城市重新通过 statement_query 查询 - 禁止从上下文中随意挑选 code，必须原样复用上次的完整 agentCodeQueries 数组. It is categorised as a Read tool in the Yjzf MCP Server, which means it retrieves data without modifying state.
Register the Yjzf MCP server in PolicyLayer and add a rule for count_all_statement: 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 Yjzf. Nothing to install.
count_all_statement 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 count_all_statement 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 count_all_statement. 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.
count_all_statement is provided by the Yjzf MCP server (@yjzf/mcp-server-yjzf). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 16 Yjzf tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.