AI agents call get_current_date_info to retrieve information from MCP System Bridge without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves current date information, a read-only operation with no capability to modify system state, execute code, or affect data. The empty description does not change this assessment given the clear semantics of the name and the server's stated purpose. Severity is low because date information is non-sensitive and retrieval has minimal blast radius.
From the tool's definition Tool name 'get_current_date_info' indicates retrieval of date/time information with no side effects. Server description confirms it 'retrieve[s] date information'. No destructive, financial, or executable operations are possible.
Documented attack patterns abuse exactly the kind of access get_current_date_info gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP System Bridge, and nothing reaches the server without passing your rules. This is the rule we recommend for get_current_date_info:
{
"version": "1",
"default": "deny",
"tools": {
"get_current_date_info": {}
}
}get_current_date_info 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.
get_current_date_info. It is categorised as a Read tool in the MCP System Bridge MCP Server, which means it retrieves data without modifying state.
Register the MCP System Bridge MCP server in PolicyLayer and add a rule for get_current_date_info: 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 System Bridge. Nothing to install.
get_current_date_info 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_date_info 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_date_info. 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_date_info is provided by the MCP System Bridge MCP server (leynier/mcp-sys-bridge). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP System Bridge, 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.
4 MCP System Bridge tools catalogued and risk-classified — across an index of 43,000+ MCP servers.