get_datetime

Get the current date and time of the machine where LMCP runs — with timezone and UTC offset. Call this whenever you need the real 'now' on the user's computer: before creating calendar events or reminders, resolving relative dates like 'today'/'tomorrow'/'next Friday', or timestamping. Takes no a...

SERVERLocal SOURCElocal-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-local-mcp-local-mcp/get-datetime.md

WHAT IT DOES

What get_datetime does on Local

AI agents call get_datetime to retrieve information from Local without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why get_datetime is rated Low

get_datetime is a pure information retrieval function that queries the system clock and returns time/timezone data. It has no ability to modify, delete, or execute operations; it merely reads and returns temporal state. This is a classic Read category tool with minimal security risk (low severity), as knowing the current time cannot directly harm the user's system or data.

From the tool's definition Tool description: 'Get the current date and time of the machine' — retrieves system time data with no side effects or modifications to any state.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_datetime safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Local, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_datetime, this is the rule to start with:

get_datetime Allowed

get_datetime is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_datetime": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Local, apply this rule, and every get_datetime call is checked against it from then on.

FAQ

Questions about get_datetime

What does the get_datetime tool do? +

How do I enforce a policy on get_datetime? +

Register the Local MCP server in PolicyLayer and add a rule for get_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 Local. Nothing to install.

What risk level is get_datetime? +

get_datetime is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_datetime? +

Yes. Add a rate_limit block to the get_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.

How do I block get_datetime completely? +

Set action: deny in the PolicyLayer policy for get_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.

What MCP server provides get_datetime? +

get_datetime is provided by the Local MCP server (local-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Local, and thousands of servers like it.

This server

All 234 Local tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →