get_current_datetime
AI agents call get_current_datetime to retrieve information from Cal Com MCP Server for Customers without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves temporal data with no side effects. It does not create, modify, delete, or execute operations. It is a simple query operation consistent with the 'Read' category. The empty description reduces confidence slightly, but the name is sufficiently explicit that the function is a straightforward data retrieval.
From the tool's definition Tool name 'get_current_datetime' indicates a read-only operation that retrieves the current date and time. No description provided, but the name clearly suggests querying system state without modification.
Attacks that exploit this kind of access
get_current_datetime. It is categorised as a Read tool in the Cal Com MCP Server for Customers MCP Server, which means it retrieves data without modifying state.
Register the Cal Com MCP Server for Customers MCP server in PolicyLayer and add a rule for get_current_datetime: 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 Cal Com MCP Server for Customers. Nothing to install.
get_current_datetime 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_datetime 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_datetime. 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_datetime is provided by the Cal Com MCP Server for Customers MCP server (niopub/calcom-mcp-for-customers). 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 →