Low Risk

date_to_timestamp

将 yyyymmdd 格式的日期转换为毫秒时间戳,计算指定日期0点的毫秒时间戳,以北京时间为基准

Part of the Yjzf MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

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

yjzf.yaml
tools:
  date_to_timestamp:
    rules:
      - action: allow

See the full Yjzf policy for all 5 tools.

Tool Name date_to_timestamp
Category Read
MCP Server Yjzf MCP Server
Risk Level Low

Agents calling read-class tools like date_to_timestamp have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.

What does the date_to_timestamp tool do? +

将 yyyymmdd 格式的日期转换为毫秒时间戳,计算指定日期0点的毫秒时间戳,以北京时间为基准. It is categorised as a Read tool in the Yjzf MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on date_to_timestamp? +

Add a rule in your Intercept YAML policy under the tools section for date_to_timestamp. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Yjzf MCP server.

What risk level is date_to_timestamp? +

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

Can I rate-limit date_to_timestamp? +

Yes. Add a rate_limit block to the date_to_timestamp rule in your Intercept 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 date_to_timestamp completely? +

Set action: deny in the Intercept 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.

What MCP server provides date_to_timestamp? +

date_to_timestamp is provided by the Yjzf MCP server (@yjzf/mcp-server-yjzf). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Yjzf

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

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

Message sent.

We'll get back to you soon.