AI agents call daily_attendance_export to retrieve information from Yjzf without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
brandId | string | Yes | 品牌ID，必须通过 brand_select 工具获取，禁止自行编造 |
endDate | string | Yes | 考勤日期截止（格式 YYYY-MM-DD）。用户未指定日期时默认取今天。必须先调用 get_current_time 获取当前时间作为参考再计算，严禁自行估算 |
branchId | string | Yes | 城市公司ID(即organId)，必须通过 branch_select 工具获取，禁止自行编造 |
cityCode | string | Yes | 城市编码，必须通过 branch_select 工具获取，禁止自行编造 |
startDate | string | Yes | 考勤日期起始（格式 YYYY-MM-DD）。用户未指定日期时默认取近31天含今天。必须先调用 get_current_time 获取当前时间作为参考再计算，严禁自行估算 |
branchName | string | Yes | 城市公司名称（用于文件命名），必须通过 branch_select 工具获取，禁止自行编造 |
departments | array | — | 部门ID列表（选填，多选）。不传则导出全部部门 |
includeResigned | boolean | — | 是否包含离职人员（选填）。不传或传 false 则不包含，传 true 则包含 |
attendanceGroups | array | — | 考勤组ID列表（选填，多选）。不传则导出全部考勤组 |
Parameters from the server's own tool schema.
This tool reads and exports attendance data into an Excel file. It is a data retrieval/export operation with no modification or deletion of records. However, it exposes sensitive employee PII (names, employee IDs, department, attendance details), raising the severity to medium despite being a read-only operation.
From the tool's definition 导出每日考勤明细Excel文件 (Export daily attendance detail Excel file) — retrieves attendance records including name, employee ID, department, attendance group, shift, date, clock-in times and results, attendance duration, late/early leave/out/make-up punches, various…
Attacks that exploit this kind of access
导出每日考勤明细Excel文件。包含姓名、工号、部门、考勤组、班次、日期、打卡时间与结果、出勤时长、迟到/早退/外出/补卡、各类假期、旷工、加班时长等完整字段。必须先调用 brand_select 获取 brandId，再调用 branch_select 获取 branchId、cityCode 和 branchName。支持多城市逐一导出。. It is categorised as a Read tool in the Yjzf MCP Server, which means it retrieves data without modifying state.
daily_attendance_export accepts 9 parameters: brandId, endDate, branchId, cityCode, startDate, branchName, departments, includeResigned, attendanceGroups. Required: brandId, endDate, branchId, cityCode, startDate, branchName. The full parameter table on this page comes from the server's own tool schema.
Register the Yjzf MCP server in PolicyLayer and add a rule for daily_attendance_export: 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.
daily_attendance_export 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 daily_attendance_export 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 daily_attendance_export. 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.
daily_attendance_export 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.
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 →