Get current server time with timezone context
AI agents call get_current_time to retrieve information from Calendar Mcp without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves timezone-aware time information from the server without modifying any calendar data, creating events, or triggering external operations. It is a straightforward query operation with minimal security impact, making it a Read category tool with low severity.
From the tool's definition Tool name 'get_current_time' and description 'Get current server time with timezone context' indicate a simple retrieval operation with no side effects or data modification.
Attacks that exploit this kind of access
Get current server time with timezone context. It is categorised as a Read tool in the Calendar Mcp MCP Server, which means it retrieves data without modifying state.
Register the Calendar MCP server in PolicyLayer and add a rule for get_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 Calendar Mcp. Nothing to install.
get_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 get_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 get_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.
get_current_time is provided by the Calendar MCP server (ydrogen/calendar-mcp). 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 →