after_sales_contract

从ERP系统导出跟单合同Excel文件。必须先调用 brand_select 获取 brandId,再调用 branch_select 获取 branchId 和 cityCode。确认城市公司(必填,支持多选)、确认交单时间范围(选填,不指定则默认本月含今天;单次最长365天,超出时提示用户缩短范围或分批导出)。状态(选填,单选,可选值: 在办单/完结单/已撤单/已交单/未交单,不传则不筛选)。

Server Yjzf @yjzf/mcp-server-yjzf
Category Read
Risk class Low
Parameters 74 required

What after_sales_contract does on Yjzf

AI agents call after_sales_contract 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.

ParameterTypeRequiredDescription
brandId string Yes 品牌ID,必须通过 brand_select 工具获取,禁止自行编造
branchId string Yes 城市公司ID(即organId),必须通过 branch_select 工具获取,禁止自行编造
cityCode string Yes 城市编码,必须通过 branch_select 工具获取,禁止自行编造
branchName string Yes 城市公司名称(用于文件命名),必须通过 branch_select 工具获取,禁止自行编造
submitEndTm number 交单结束时间(毫秒时间戳)。用户有指定日期时,必须先调用 get_current_time 获取当前时间作为参考,再用 date_to_timestamp(endOfDay=true) 转换,严禁自行估算。不传默认今天结束。时间范围最长不超过365天,超出时提示用户缩短范围或分批导出
submitStartTm number 交单开始时间(毫秒时间戳)。用户有指定日期时,必须先调用 get_current_time 获取当前时间作为参考,再用 date_to_timestamp 转换,严禁自行估算。不传默认本月第一天。时间范围最长不超过365天,超出时提示用户缩短范围或分批导出
contractStatus string 状态(单选),选填。可选值: 2=在办单, 4,32,64=完结单, 8,16=已撤单, 1=已交单, 0=未交单。用户说'不限'或无指定状态时,不传此参数即可。不传则不按状态筛选

Parameters from the server's own tool schema.

Why after_sales_contract needs a policy

This tool exports/reads contract data from an ERP system into an Excel file. It retrieves existing records without modifying them. The medium severity reflects that it accesses potentially sensitive business contract data that could be misused if exported inappropriately, but it performs no write or destructive operations.

From the tool's definition 导出跟单合同Excel文件 (export after-sales contract Excel file from ERP system)

Questions about after_sales_contract

What does the after_sales_contract tool do? +

从ERP系统导出跟单合同Excel文件。必须先调用 brand_select 获取 brandId,再调用 branch_select 获取 branchId 和 cityCode。确认城市公司(必填,支持多选)、确认交单时间范围(选填,不指定则默认本月含今天;单次最长365天,超出时提示用户缩短范围或分批导出)。状态(选填,单选,可选值: 在办单/完结单/已撤单/已交单/未交单,不传则不筛选)。. It is categorised as a Read tool in the Yjzf MCP Server, which means it retrieves data without modifying state.

What parameters does after_sales_contract accept? +

after_sales_contract accepts 7 parameters: brandId, branchId, cityCode, branchName, submitEndTm, submitStartTm, contractStatus. Required: brandId, branchId, cityCode, branchName. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on after_sales_contract? +

Register the Yjzf MCP server in PolicyLayer and add a rule for after_sales_contract: 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.

What risk level is after_sales_contract? +

after_sales_contract is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit after_sales_contract? +

Yes. Add a rate_limit block to the after_sales_contract 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.

How do I block after_sales_contract completely? +

Set action: deny in the PolicyLayer policy for after_sales_contract. 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.

What MCP server provides after_sales_contract? +

after_sales_contract 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.

// THE FULL RECORD

after_sales_contract is one line of Yjzf's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.