global-health-covid.epidemiology.location_search

SERVERApibase SOURCEapibase-mcp-client

Low RISK CLASS

Category Read

Parameters 30 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-search.md

WHAT IT DOES

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

AI agents call global-health-covid.epidemiology.location_search 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
`query`	string	—	Free-text match against country, subregion, or locality name (e.g. "California", "Germany"). Case-insensitive substring match. Omit to browse by country_code/ag
`country_code`	string	—	Filter to a single 2-letter ISO country code (e.g. "US", "DE").
`aggregation_level`	string	—	Filter by administrative level: "0"=country, "1"=state/province, "2"=county, "3"=locality/city.

Parameters from the server's own tool schema.

RISK

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

Tool queries and retrieves historical COVID-19 location data without creating, modifying, or deleting information.

From the tool's definition Search/list COVID-19 tracked locations by free-text name, returns location key and names.

Risk signalsBulk/mass operation — affects multiple targets · Admin/system-level operation

Attacks that exploit this kind of access

RECOMMENDED RULE

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

global-health-covid.epidemiology.location_search Allowed

global-health-covid.epidemiology.location_search 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_search": {}
  }
}

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_search call is checked against it from then on.

FAQ

Questions about global-health-covid.epidemiology.location_search

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

Search/list COVID-19 tracked locations (countries, states/provinces, counties, localities) by free-text name, ISO country code, and/or administrative aggregation level. Returns each location's key, names, and level — use the returned location_key with global-health-covid.latest_snapshot or global-health-covid.location_history. Data: Google "COVID-19 Open Data" (storage.googleapis.com/covid19-open-data), no auth required. HISTORICAL DATA ONLY — frozen since 2022-09-15. 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_search accept? +

global-health-covid.epidemiology.location_search accepts 3 parameters: query, country_code, aggregation_level. 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_search? +

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

global-health-covid.epidemiology.location_search 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_search? +

Yes. Add a rate_limit block to the global-health-covid.epidemiology.location_search 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_search completely? +

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

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

evaluate_search_quality on ACE-MCP →search_torrents on M-Team MCP Server →aiva_search_customers on AIVA MCP Server →search_channel on YouTube MCP Server → The MCP Attack Database →

Guides

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