getDayInHistory
Returns historical events that happened on a given month and day. Free requests cover today's date only; other dates plus limit and offset require premium.
This record as markdown: /tools/com-api-ninjas-mcp/getdayinhistory.md
What getDayInHistory does on API Ninjas
AI agents call getDayInHistory to retrieve information from API Ninjas without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
day | integer | — | The day of the month for the historical events to retrieve. Must be between 1 and 31. If specified, month must also be provided. If both are omitted, today's da |
limit | integer | — | The maximum number of results to return. Must be between 1 and 30. Default is 1. Premium only. |
month | integer | — | The month of the historical events to retrieve. Must be between 1 and 12. If specified, day must also be provided. If both are omitted, today's date is used. Pr |
offset | integer | — | The number of results to skip. Must be zero or a positive integer. Default is 0. Premium only. |
Parameters from the server's own tool schema.
Why getDayInHistory is rated Low
Even though getDayInHistory only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs getDayInHistory safely
PolicyLayer is an MCP gateway: it sits between your AI agents and API Ninjas, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For getDayInHistory, this is the rule to start with:
getDayInHistory is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect API Ninjas, apply this rule, and every getDayInHistory call is checked against it from then on.
Questions about getDayInHistory
Returns historical events that happened on a given month and day. Free requests cover today's date only; other dates plus limit and offset require premium. It is categorised as a Read tool in the API Ninjas MCP Server, which means it retrieves data without modifying state.
getDayInHistory accepts 4 parameters: day, limit, month, offset. The full parameter table on this page comes from the server's own tool schema.
Register the API Ninjas MCP server in PolicyLayer and add a rule for getDayInHistory: 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 API Ninjas. Nothing to install.
getDayInHistory 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 getDayInHistory 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 getDayInHistory. 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.
getDayInHistory is provided by the API Ninjas MCP server (https://mcp.api-ninjas.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on API Ninjas, and thousands of servers like it.
This server
Across the catalogue