Get current date and time with rich temporal context for LLM awareness. Provides human-readable format, timezone info, calendar context (quarter, week, day-of-year), and relative calculations.
AI agents call get_current_datetime to retrieve information from MCP DevTools Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only reads and returns temporal data without side effects. It queries system time information to provide context to the LLM. This is a pure read operation with no capability to modify state, execute arbitrary code, or cause harm. Severity is low as misuse would only provide incorrect temporal context to an AI agent.
From the tool's definition Tool retrieves current date and time with temporal context; description indicates 'Get current date and time' with information provision ('Provides human-readable format, timezone info, calendar context').
Documented attack patterns abuse exactly the kind of access get_current_datetime gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP DevTools Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_current_datetime:
{
"version": "1",
"default": "deny",
"tools": {
"get_current_datetime": {}
}
}get_current_datetime 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 current date and time with rich temporal context for LLM awareness. Provides human-readable format, timezone info, calendar context (quarter, week, day-of-year), and relative calculations. It is categorised as a Read tool in the MCP DevTools Server MCP Server, which means it retrieves data without modifying state.
Register the MCP DevTools Server MCP server in PolicyLayer and add a rule for get_current_datetime: 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 MCP DevTools Server. Nothing to install.
get_current_datetime 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 get_current_datetime 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 get_current_datetime. 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.
get_current_datetime is provided by the MCP DevTools Server MCP server (rshade/mcp-devtools-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP DevTools Server, 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.
79 MCP DevTools Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.