New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

brightsky.stations.nearby

Find DWD (Deutscher Wetterdienst) weather stations near a given latitude/longitude in Germany. Returns each station's DWD station ID, WMO station ID, name, coordinates, elevation, observation type (current / recent / historical / forecast), date range of available records, and distance from the q...

SERVERApibase SOURCEapibase-mcp-client
Low RISK CLASS
Category Read
Parameters 32 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-whiteknightonhorse-apibase/brightsky.stations.nearby.md

What brightsky.stations.nearby does on Apibase

AI agents call brightsky.stations.nearby 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.

ParameterTypeRequiredDescription
latitude number Yes Latitude of the location in Germany (e.g. 52.52 for Berlin, range 47–56)
max_dist number — Maximum distance in metres from the given coordinates to include stations. When omitted, all DWD stations are returned sorted by proximity.
longitude number Yes Longitude of the location in Germany (e.g. 13.40 for Berlin, range 5–16)

Parameters from the server's own tool schema.

Why brightsky.stations.nearby is rated Low

Tool queries and returns weather station metadata without modifying data or executing operations.

From the tool's definition Find weather stations, returns station data, no side effects

Questions about brightsky.stations.nearby

What does the brightsky.stations.nearby tool do? +

Find DWD (Deutscher Wetterdienst) weather stations near a given latitude/longitude in Germany. Returns each station's DWD station ID, WMO station ID, name, coordinates, elevation, observation type (current / recent / historical / forecast), date range of available records, and distance from the query point. Useful for discovering which stations cover a location before querying observations or synop data. No distance filter by default — returns all matching sources sorted by proximity. No API key required — open DWD data via Bright Sky (MIT licence). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.

What parameters does brightsky.stations.nearby accept? +

brightsky.stations.nearby accepts 3 parameters: latitude, max_dist, longitude. Required: latitude, longitude. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on brightsky.stations.nearby? +

Register the Apibase MCP server in PolicyLayer and add a rule for brightsky.stations.nearby: 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 brightsky.stations.nearby? +

brightsky.stations.nearby is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit brightsky.stations.nearby? +

Yes. Add a rate_limit block to the brightsky.stations.nearby 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 brightsky.stations.nearby completely? +

Set action: deny in the PolicyLayer policy for brightsky.stations.nearby. 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 brightsky.stations.nearby? +

brightsky.stations.nearby 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.

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Apibase's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.