Low Risk

getCurrentDate

获取当前日期 - 返回格式为 yyyy-MM-dd 的当前日期字符串

How to control getCurrentDate ↓

AI agents call getCurrentDate to retrieve information from Flight Ticket MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

This tool retrieves the current date and returns it as a formatted string. It performs a read-only query of system state with no capability to modify, delete, or execute any operations. The blast radius of misuse is minimal as it only exposes non-sensitive temporal information.

From the tool's definition Tool name is 'getCurrentDate' and description states it 'returns current date string in yyyy-MM-dd format'. This is a simple data retrieval operation with no side effects.

Documented attack patterns abuse exactly the kind of access getCurrentDate gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and Flight Ticket MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for getCurrentDate:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "getCurrentDate": {}
  }
}

getCurrentDate is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Flight Ticket MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the getCurrentDate tool do? +

获取当前日期 - 返回格式为 yyyy-MM-dd 的当前日期字符串. It is categorised as a Read tool in the Flight Ticket MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on getCurrentDate? +

Register the Flight Ticket MCP Server MCP server in PolicyLayer and add a rule for getCurrentDate: 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 Flight Ticket MCP Server. Nothing to install.

What risk level is getCurrentDate? +

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

Can I rate-limit getCurrentDate? +

Yes. Add a rate_limit block to the getCurrentDate 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 getCurrentDate completely? +

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

getCurrentDate is provided by the Flight Ticket MCP Server MCP server (xiaonieli7/flightticketmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Flight Ticket MCP Server tool call.

Deterministic rules across all 10 Flight Ticket MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

10 Flight Ticket MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.