gov.sg.weather_forecast
Real-time 2-hour weather forecast for 51 Singapore zones (showers/cloudy/etc.) from NEA. Singapore Open Data Licence v1.0
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/gov.sg.weather-forecast.md
What gov.sg.weather_forecast does on Apibase
AI agents call gov.sg.weather_forecast 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 |
|---|---|---|---|
date | string | — | Optional ISO 8601 date (YYYY-MM-DD) or datetime to query historical data. If omitted, returns the latest snapshot. |
Parameters from the server's own tool schema.
Why gov.sg.weather_forecast is rated Low
Queries weather data with no ability to modify, delete, or execute operations.
From the tool's definition Real-time weather forecast, retrieves data from NEA, no side effects.
Attacks that exploit this kind of access
The rule that runs gov.sg.weather_forecast 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 gov.sg.weather_forecast, this is the rule to start with:
gov.sg.weather_forecast 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 gov.sg.weather_forecast call is checked against it from then on.
Questions about gov.sg.weather_forecast
Real-time 2-hour weather forecast for 51 Singapore zones (showers/cloudy/etc.) from NEA. Singapore Open Data Licence v1.0. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
gov.sg.weather_forecast accepts 1 parameter: date. 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 gov.sg.weather_forecast: 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.
gov.sg.weather_forecast 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 gov.sg.weather_forecast 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 gov.sg.weather_forecast. 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.
gov.sg.weather_forecast 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