global-health-covid.epidemiology.location_history

SERVERApibase SOURCEapibase-mcp-client

Low RISK CLASS

Category Read

Parameters 31 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-whiteknightonhorse-apibase/global-health-covid.epidemiology.location-history.md

WHAT IT DOES

What global-health-covid.epidemiology.location_history does on Apibase

AI agents call global-health-covid.epidemiology.location_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
`end_date`	string	—	Filter history to dates on/before this ISO date, format "YYYY-MM-DD". Omit for full history.
`start_date`	string	—	Filter history to dates on/after this ISO date, format "YYYY-MM-DD". Omit for full history.
`location_key`	string	Yes	Location key from the dataset, e.g. "US" (country), "US_CA" (state), or a deeper key discovered via global-health-covid.location_search.

Parameters from the server's own tool schema.

RISK

Why global-health-covid.epidemiology.location_history is rated Low

Retrieves historical epidemiological data with no side effects or modifications.

From the tool's definition Get the full daily historical COVID-19 time series for one location, optionally windowed by start_date/end_date.

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs global-health-covid.epidemiology.location_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 global-health-covid.epidemiology.location_history, this is the rule to start with:

global-health-covid.epidemiology.location_history Allowed

global-health-covid.epidemiology.location_history is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "global-health-covid.epidemiology.location_history": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Apibase, apply this rule, and every global-health-covid.epidemiology.location_history call is checked against it from then on.

FAQ

Questions about global-health-covid.epidemiology.location_history

What does the global-health-covid.epidemiology.location_history tool do? +

Get the full daily historical COVID-19 time series for one location, optionally windowed by start_date/end_date. Returns a curated subset of core fields per day: cases, deaths, hospitalizations, and vaccination totals (both new and cumulative), plus population. Does NOT return the raw upstream dataset which includes 700+ demographic/policy/search-trend columns. Use global-health-covid.location_search first to find a valid location_key. Data: Google "COVID-19 Open Data" (storage.googleapis.com/covid19-open-data), no auth required. HISTORICAL DATA ONLY — coverage ends ~2022-09, frozen dataset. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.

What parameters does global-health-covid.epidemiology.location_history accept? +

global-health-covid.epidemiology.location_history accepts 3 parameters: end_date, start_date, location_key. Required: location_key. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on global-health-covid.epidemiology.location_history? +

Register the Apibase MCP server in PolicyLayer and add a rule for global-health-covid.epidemiology.location_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.

What risk level is global-health-covid.epidemiology.location_history? +

global-health-covid.epidemiology.location_history is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit global-health-covid.epidemiology.location_history? +

Yes. Add a rate_limit block to the global-health-covid.epidemiology.location_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.

How do I block global-health-covid.epidemiology.location_history completely? +

Set action: deny in the PolicyLayer policy for global-health-covid.epidemiology.location_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.

What MCP server provides global-health-covid.epidemiology.location_history? +

global-health-covid.epidemiology.location_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.

KEEP EXPLORING

More on Apibase, and thousands of servers like it.

This server

All 1384 Apibase tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →