Get the current system date and time for creating events
AI agents call get_current_time to retrieve information from Google Calendar MCP Server 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 date and time from the system. It performs no modifications, deletions, or state changes. It is informational only and poses minimal security risk. Even in the context of a calendar management server, this specific tool cannot create, modify, or delete events — it only supplies a timestamp value useful for downstream operations.
From the tool's definition Tool description states 'Get the current system date and time' — a pure retrieval operation with no side effects. The name 'get_current_time' and verb 'Get' further confirm read-only intent.
Attacks that exploit this kind of access
Get the current system date and time for creating events. It is categorised as a Read tool in the Google Calendar MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Google Calendar MCP Server 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 Google Calendar MCP Server. 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 Google Calendar MCP Server MCP server (kashyab19/google-calendar-mcp-server). 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 →