AI agents call current_datetime to retrieve information from brainMD without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves temporal information without modifying any state, creating data, or triggering external operations. It is a simple informational read operation typical of system utilities. The minimal description does not suggest any dangerous capability. Classification as Read with low severity is appropriate; misuse poses negligible risk.
From the tool's definition Tool named 'current_datetime' with description 'Server' - returns the current date and time, a read-only operation with no side effects or data modification.
Documented attack patterns abuse exactly the kind of access current_datetime gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and brainMD, and nothing reaches the server without passing your rules. This is the rule we recommend for current_datetime:
{
"version": "1",
"default": "deny",
"tools": {
"current_datetime": {}
}
}current_datetime is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Server. It is categorised as a Read tool in the brainMD MCP Server, which means it retrieves data without modifying state.
Register the brainMD MCP server in PolicyLayer and add a rule for 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 brainMD. Nothing to install.
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 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 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.
current_datetime is provided by the brainMD MCP server (mi4uu/brain.md). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from brainMD, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
17 brainMD tools catalogued and risk-classified — across an index of 43,000+ MCP servers.