getHistoricalEvents
Searches famous events in history by keyword text and/or year, month and day; negative years mean BC. Pagination with offset requires premium.
This record as markdown: /tools/com-api-ninjas-mcp/gethistoricalevents.md
What getHistoricalEvents does on API Ninjas
AI agents call getHistoricalEvents 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 | — | Calendar day of the month. |
text | string | — | Query text to search events by. Use keywords or short phrases for best match results. |
year | integer | — | 4-digit year (e.g. 1776). For BC/BCE years, use a negative integer (e.g. -351 for 351 BC). |
month | integer | — | Integer month (e.g. 3 for March). |
offset | integer | — | Number of results to offset pagination. Premium only. |
Parameters from the server's own tool schema.
Why getHistoricalEvents is rated Low
Even though getHistoricalEvents 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 getHistoricalEvents 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 getHistoricalEvents, this is the rule to start with:
getHistoricalEvents 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 getHistoricalEvents call is checked against it from then on.
Questions about getHistoricalEvents
Searches famous events in history by keyword text and/or year, month and day; negative years mean BC. Pagination with offset requires premium. It is categorised as a Read tool in the API Ninjas MCP Server, which means it retrieves data without modifying state.
getHistoricalEvents accepts 5 parameters: day, text, year, 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 getHistoricalEvents: 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.
getHistoricalEvents 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 getHistoricalEvents 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 getHistoricalEvents. 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.
getHistoricalEvents 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