AI agents call today to retrieve information from Travel without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a read-only operation that retrieves the current date. It has no capability to modify, delete, or execute operations. The minimal description limits confidence slightly, but the functionality is straightforward and poses minimal risk if misused by an agent.
From the tool's definition Tool name 'today' with description 'get today' indicates retrieval of the current date/time. No parameters are described, suggesting it simply returns data without side effects.
Documented attack patterns abuse exactly the kind of access today gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Travel, and nothing reaches the server without passing your rules. This is the rule we recommend for today:
{
"version": "1",
"default": "deny",
"tools": {
"today": {}
}
}today is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
get today. It is categorised as a Read tool in the Travel MCP Server, which means it retrieves data without modifying state.
Register the Travel MCP server in PolicyLayer and add a rule for today: 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 Travel. Nothing to install.
today is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the today 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 today. 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.
today is provided by the Travel MCP server (prakashsanker/flights-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Travel, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
3 Travel tools catalogued and risk-classified — across an index of 43,000+ MCP servers.