disease.covid.history
Get historical time-series COVID-19 data for a country or globally. Returns daily case, death, and recovery counts. Useful for trend analysis and longitudinal research. Data from Johns Hopkins CSSE.
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/disease.covid.history.md
What disease.covid.history does on Apibase
AI agents call disease.covid.history to retrieve information from Apibase 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 |
|---|---|---|---|
country | string | — | Country name, ISO2/ISO3 code, or "all" for global aggregate (default "all") |
lastdays | integer | — | Number of most recent days to return (default 30, max ~1500 for full history) |
Parameters from the server's own tool schema.
Why disease.covid.history is rated Low
Retrieves public epidemiological data without modifying or executing operations.
From the tool's definition Get historical time-series COVID-19 data. Returns daily case, death, and recovery counts.
Attacks that exploit this kind of access
The rule that runs disease.covid.history safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For disease.covid.history, this is the rule to start with:
disease.covid.history 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 Apibase, apply this rule, and every disease.covid.history call is checked against it from then on.
Questions about disease.covid.history
Get historical time-series COVID-19 data for a country or globally. Returns daily case, death, and recovery counts. Useful for trend analysis and longitudinal research. Data from Johns Hopkins CSSE. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
disease.covid.history accepts 2 parameters: country, lastdays. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for disease.covid.history: 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 Apibase. Nothing to install.
disease.covid.history 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 disease.covid.history 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 disease.covid.history. 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.
disease.covid.history is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue