ukhsa-dashboard.metrics.data
Get paginated timeseries data points for one UK health surveillance metric (cases, deaths, healthcare admissions, testing, vaccinations, etc.) at a specific geography, identified by the full theme/sub_theme/topic/geography_type/geography/metric path from ukhsa-dashboard.browse. Optional filters: ...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/ukhsa-dashboard.metrics.data.md
What ukhsa-dashboard.metrics.data does on Apibase
AI agents call ukhsa-dashboard.metrics.data 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 |
|---|---|---|---|
age | string | — | Filter by age band as published for this metric (e.g. "all", "15-44") |
sex | string | — | Filter by sex as published for this metric (e.g. "all", "f", "m") |
date | string | — | Filter to a single exact date, YYYY-MM-DD (e.g. "2023-06-15") |
page | integer | — | Page number of results (default 1) |
year | integer | — | Filter to a single calendar year (e.g. 2023) |
theme | string | Yes | Top-level theme slug (e.g. "infectious_disease") |
topic | string | Yes | Disease/topic slug (e.g. "COVID-19") |
metric | string | Yes | Metric name from ukhsa-dashboard.browse at the metrics level (e.g. "COVID-19_cases_casesByDay") |
epiweek | integer | — | Filter to a single epidemiological week number (1-53) |
stratum | string | — | Filter by stratum/breakdown as published for this metric (e.g. "default") |
geography | string | Yes | Geography name (e.g. "England") |
page_size | integer | — | Number of data points per page (1-500, default 100) |
Parameters from the server's own tool schema.
Why ukhsa-dashboard.metrics.data is rated Low
Retrieves public health surveillance data with no side effects or modifications.
From the tool's definition Get paginated timeseries data points for one UK health surveillance metric
Risk signalsHigh parameter count (15 properties)
Attacks that exploit this kind of access
The rule that runs ukhsa-dashboard.metrics.data 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 ukhsa-dashboard.metrics.data, this is the rule to start with:
ukhsa-dashboard.metrics.data 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 ukhsa-dashboard.metrics.data call is checked against it from then on.
Questions about ukhsa-dashboard.metrics.data
Get paginated timeseries data points for one UK health surveillance metric (cases, deaths, healthcare admissions, testing, vaccinations, etc.) at a specific geography, identified by the full theme/sub_theme/topic/geography_type/geography/metric path from ukhsa-dashboard.browse. Optional filters: year, epiweek, exact date, age band, sex, stratum, and reporting-delay-period flag. Data: api.ukhsa-dashboard.data.gov.uk, UK Open Government Licence v3.0, no auth required. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
ukhsa-dashboard.metrics.data accepts 12 parameters: age, sex, date, page, year, theme, topic, metric, epiweek, stratum, geography, page_size. Required: theme, topic, metric, geography. 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 ukhsa-dashboard.metrics.data: 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.
ukhsa-dashboard.metrics.data 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 ukhsa-dashboard.metrics.data 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 ukhsa-dashboard.metrics.data. 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.
ukhsa-dashboard.metrics.data 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