AI agents call datetime.health to retrieve information from Datetime without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Health check tools are purely informational and return status without modifying state, executing arbitrary code, or causing side effects. This is consistent with the Read category. Confidence is moderate (0.7) rather than high because the description is empty, leaving some ambiguity about the tool's precise function, though the name and server context strongly suggest a benign status query.
From the tool's definition Tool name 'datetime.health' suggests a health check or status query operation. The server description indicates this is a 'lightweight MCP server that provides date and time tools' with capabilities to 'retrieve current timestamps' and 'interact with the host…
Documented attack patterns abuse exactly the kind of access datetime.health gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Datetime, and nothing reaches the server without passing your rules. This is the rule we recommend for datetime.health:
{
"version": "1",
"default": "deny",
"tools": {
"datetime.health": {}
}
}datetime.health 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.
datetime.health. It is categorised as a Read tool in the Datetime MCP Server, which means it retrieves data without modifying state.
Register the Datetime MCP server in PolicyLayer and add a rule for datetime.health: 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 Datetime. Nothing to install.
datetime.health 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 datetime.health 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 datetime.health. 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.
datetime.health is provided by the Datetime MCP server (joshuaboys/datetime-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Datetime, 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 Datetime tools catalogued and risk-classified — across an index of 43,000+ MCP servers.