# get-current-date

获取当前日期，以上海时区（Asia/Shanghai, UTC+8）为准，返回格式为 "yyyy-MM-dd"。主要用于解析用户提到的相对日期（如“明天”、“下周三”），为其他需要日期的接口提供准确的日期输入。

Agent View of the PolicyLayer registry record for `get-current-date`. HTML page: https://policylayer.com/tools/deniselewis200081-rail/get-current-date

## Facts

- Tool: `get-current-date`
- Server: 12306 Ticket Search Server (`DeniseLewis200081/rail`) — https://policylayer.com/tools/deniselewis200081-rail.md
- Homepage: https://github.com/DeniseLewis200081/rail
- Risk category: Read (Low risk)
- Registry record: grade A, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Allowed

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "get-current-date",
    "arguments": {}
  }
}
```

## Why get-current-date is rated Low

This tool performs a simple read operation that retrieves the current date in Shanghai timezone. It has no ability to modify, delete, execute code, or affect financial systems. The purpose is to provide date context for parsing relative date references in user queries. The blast radius of misuse is negligible—an AI agent cannot cause harm by calling this tool repeatedly or with any arguments.

From the tool's own definition: "Tool description indicates it 'gets current date' (获取当前日期) and 'returns format as yyyy-MM-dd'. It retrieves system date information with no side effects or data modifications."

## Use case

AI agents call get-current-date to retrieve information from 12306 Ticket Search Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches 12306 Ticket Search Server:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get-current-date": {}
  }
}
```

## Other tools on 12306 Ticket Search Server (7)

- `get-interline-tickets` — Read — https://policylayer.com/tools/deniselewis200081-rail/get-interline-tickets.md
- `get-station-by-telecode` — Read — https://policylayer.com/tools/deniselewis200081-rail/get-station-by-telecode.md
- `get-station-code-by-names` — Read — https://policylayer.com/tools/deniselewis200081-rail/get-station-code-by-names.md
- `get-station-code-of-citys` — Read — https://policylayer.com/tools/deniselewis200081-rail/get-station-code-of-citys.md
- `get-stations-code-in-city` — Read — https://policylayer.com/tools/deniselewis200081-rail/get-stations-code-in-city.md
- `get-tickets` — Read — https://policylayer.com/tools/deniselewis200081-rail/get-tickets.md
- `get-train-route-stations` — Read — https://policylayer.com/tools/deniselewis200081-rail/get-train-route-stations.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=deniselewis200081-rail · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/deniselewis200081-rail