Low Risk

get_current_datetime

Get the current date and time in the configured timezone.

How to control get_current_datetime ↓

AI agents call get_current_datetime to retrieve information from MCP SearXNG Enhanced without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

This tool performs a simple read operation that returns temporal information without creating, modifying, deleting, or executing any external operations. The "configured timezone" parameter indicates it queries existing configuration rather than changing system state.

From the tool's definition get_current_datetime retrieves current date/time information with no side effects or modifications to any system state.

Documented attack patterns abuse exactly the kind of access get_current_datetime gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and MCP SearXNG Enhanced, and nothing reaches the server without passing your rules. This is the rule we recommend for get_current_datetime:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_current_datetime": {}
  }
}

get_current_datetime is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register MCP SearXNG Enhanced — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the get_current_datetime tool do? +

Get the current date and time in the configured timezone. It is categorised as a Read tool in the MCP SearXNG Enhanced MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_current_datetime? +

Register the MCP SearXNG Enhanced 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 MCP SearXNG Enhanced. Nothing to install.

What risk level is get_current_datetime? +

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

Can I rate-limit get_current_datetime? +

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.

How do I block get_current_datetime completely? +

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.

What MCP server provides get_current_datetime? +

get_current_datetime is provided by the MCP SearXNG Enhanced MCP server (overtlids/mcp-searxng-enhanced). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every MCP SearXNG Enhanced tool call.

Deterministic rules across all 3 MCP SearXNG Enhanced tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

3 MCP SearXNG Enhanced tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.