date \u00b7 GET /date/getCurrentDate \u2014 Get current date.
AI agents call date_get_current_date to retrieve information from Vicarius vRx MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns the current date—a passive information retrieval with no ability to modify, delete, or execute operations. It poses minimal risk as it cannot alter system state or commit financial actions. Classification as Read is appropriate.
From the tool's definition Tool name 'date_get_current_date' and description 'Get current date' indicate a simple retrieval operation with no side effects. The GET HTTP method confirms read-only access.
Attacks that exploit this kind of access
date \u00b7 GET /date/getCurrentDate \u2014 Get current date. It is categorised as a Read tool in the Vicarius vRx MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Vicarius vRx MCP Server MCP server in PolicyLayer and add a rule for date_get_current_date: 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 Vicarius vRx MCP Server. Nothing to install.
date_get_current_date 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 date_get_current_date 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 date_get_current_date. 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.
date_get_current_date is provided by the Vicarius vRx MCP Server MCP server (space-c0wboy/vicarius-vrx-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 →