msc-geomet.climate.stations
Search the Environment and Climate Change Canada climate station catalog by province/ territory or bounding box. Returns each station's CLIMATE_IDENTIFIER (needed for msc-geomet.climate_daily), coordinates, elevation, and its daily/hourly record date ranges. Data: api.weather.gc.ca (MSC GeoMet OG...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/msc-geomet.climate.stations.md
What msc-geomet.climate.stations does on Apibase
AI agents call msc-geomet.climate.stations 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 |
|---|---|---|---|
bbox | string | — | Bounding box filter as "minLon,minLat,maxLon,maxLat" in decimal degrees (e.g. "-80,43,-79,44" for the Toronto area). |
limit | integer | — | Max records to return (1-100). Defaults to 20. |
province | string | — | Filter to a Canadian province/territory by 2-letter code (e.g. "ON" Ontario, "BC" British Columbia). Omit to search all provinces. |
Parameters from the server's own tool schema.
Why msc-geomet.climate.stations is rated Low
Tool queries public climate station metadata with no side effects or data modification capabilities.
From the tool's definition Search...catalog, Returns...coordinates, elevation, record date ranges
Attacks that exploit this kind of access
The rule that runs msc-geomet.climate.stations 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.climate.stations, this is the rule to start with:
msc-geomet.climate.stations 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.climate.stations call is checked against it from then on.
Questions about msc-geomet.climate.stations
Search the Environment and Climate Change Canada climate station catalog by province/ territory or bounding box. Returns each station's CLIMATE_IDENTIFIER (needed for msc-geomet.climate_daily), coordinates, elevation, and its daily/hourly record date ranges. Data: api.weather.gc.ca (MSC GeoMet OGC API - Features), 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.climate.stations accepts 3 parameters: bbox, limit, province. 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.climate.stations: 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.climate.stations 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.climate.stations 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.climate.stations. 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.climate.stations 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