将 yyyymmdd 格式的日期转换为毫秒时间戳（北京时间）。默认返回当天 00:00:00 的时间戳，传 endOfDay=true 返回当天 23:59:59.999 的时间戳。用于 startTime 时不传 endOfDay，用于 endTime 时传 endOfDay=true
Part of the Yjzf server.
Free to start. No card required.
AI agents invoke date_to_timestamp to trigger processes or run actions in Yjzf. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.
date_to_timestamp can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. PolicyLayer enforces rate limits and validates arguments to keep execution within safe bounds.
Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.
{
"version": "1",
"default": "deny",
"tools": {
"date_to_timestamp": {
"limits": [
{
"counter": "date_to_timestamp_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}See the full Yjzf policy for all 16 tools.
These attack patterns abuse exactly the kind of access date_to_timestamp gives an agent. Each links to the full case and the policy that stops it:
Other execute tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
将 yyyymmdd 格式的日期转换为毫秒时间戳（北京时间）。默认返回当天 00:00:00 的时间戳，传 endOfDay=true 返回当天 23:59:59.999 的时间戳。用于 startTime 时不传 endOfDay，用于 endTime 时传 endOfDay=true. It is categorised as a Execute tool in the Yjzf MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Yjzf MCP server in PolicyLayer and add a rule for date_to_timestamp: 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.
date_to_timestamp is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the date_to_timestamp 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 date_to_timestamp. 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.
date_to_timestamp 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.