msc-geomet.hydrometric.realtime
Get real-time water level (m) and discharge (m3/s) readings for a Canadian river or lake by hydrometric station_number, sorted most-recent-first. Readings are typically reported every 5 minutes for stations with real-time telemetry. Data: api.weather.gc.ca (MSC GeoMet OGC API - Features, sourced ...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/msc-geomet.hydrometric.realtime.md
What msc-geomet.hydrometric.realtime does on Apibase
AI agents call msc-geomet.hydrometric.realtime 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 |
|---|---|---|---|
limit | integer | — | Max records to return (1-288). Defaults to 20. |
station_number | string | Yes | Hydrometric station number, e.g. "01AD003" (St. Francis River, NB). Readings are reported roughly every 5 minutes for stations with real-time telemetry. |
Parameters from the server's own tool schema.
Why msc-geomet.hydrometric.realtime is rated Low
Retrieves hydrometric data with no side effects or modifications possible.
From the tool's definition Get real-time water level and discharge readings
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs msc-geomet.hydrometric.realtime 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 msc-geomet.hydrometric.realtime, this is the rule to start with:
msc-geomet.hydrometric.realtime 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 msc-geomet.hydrometric.realtime call is checked against it from then on.
Questions about msc-geomet.hydrometric.realtime
Get real-time water level (m) and discharge (m3/s) readings for a Canadian river or lake by hydrometric station_number, sorted most-recent-first. Readings are typically reported every 5 minutes for stations with real-time telemetry. Data: api.weather.gc.ca (MSC GeoMet OGC API - Features, sourced from HYDAT/WSC), no auth required. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
msc-geomet.hydrometric.realtime accepts 2 parameters: limit, station_number. Required: station_number. 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 msc-geomet.hydrometric.realtime: 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.
msc-geomet.hydrometric.realtime 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 msc-geomet.hydrometric.realtime 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 msc-geomet.hydrometric.realtime. 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.
msc-geomet.hydrometric.realtime 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