Low Risk

date_fact

Get historical facts about a calendar date (e.g., "3/14" for March 14). Returns the fact and date.

Part of the Numuersapi server.

date_fact is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE NUMUERSAPI →

Free to start. No card required.

AI agents call date_fact to retrieve information from Numuersapi without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though date_fact only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

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

See the full Numuersapi policy for all 24 tools.

Get this rule live on your own Numuersapi server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY NUMUERSAPI →

View all 24 tools →

These attack patterns abuse exactly the kind of access date_fact gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so date_fact only ever does what you allow.

SECURE NUMUERSAPI →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the date_fact tool do? +

Get historical facts about a calendar date (e.g., "3/14" for March 14). Returns the fact and date.. It is categorised as a Read tool in the Numuersapi MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on date_fact? +

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

What risk level is date_fact? +

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

Can I rate-limit date_fact? +

Yes. Add a rate_limit block to the date_fact 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 date_fact completely? +

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

date_fact is provided by the Numuersapi MCP server (https://gateway.pipeworx.io/numbersapi/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Numuersapi tool call.

Deterministic rules across all 24 Numuersapi tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.