Return the current local time.
AI agents call current_time to retrieve information from DateTime-LocalMCPServer without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only retrieves the current local time from the host environment with no side effects, no data modification, and no external operations. It is a pure read/query operation with minimal blast radius.
From the tool's definition Return the current local time
Attacks that exploit this kind of access
Return the current local time. It is categorised as a Read tool in the DateTime-LocalMCPServer MCP Server, which means it retrieves data without modifying state.
Register the DateTime-LocalMCPServer MCP server in PolicyLayer and add a rule for current_time: 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-LocalMCPServer. Nothing to install.
current_time 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 current_time 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 current_time. 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.
current_time is provided by the DateTime-LocalMCPServer MCP server (vikasprajapati1998/datetime-localmcpserver). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →