get_current_time
AI agents call get_current_time to retrieve information from Calendar App without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves current time data with no side effects, no data modification, and no external operations triggered. It is a read-only query operation that fits the Read category. The lack of descriptive text slightly lowers confidence, but the naming convention strongly suggests a simple getter function.
From the tool's definition Tool name is 'get_current_time' with empty description. Based on sibling tools ('get_events', 'get_reminders', 'get_today_summary', 'list_calendars', 'list_timezones') and the server's stated purpose of accessing and interacting with calendar data, this tool…
Attacks that exploit this kind of access
get_current_time. It is categorised as a Read tool in the Calendar App MCP Server, which means it retrieves data without modifying state.
Register the Calendar App 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 App. 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 App MCP server (rygwdn/calendar-app-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 →