Check the operational status of the NOAA and Open-Meteo weather APIs. Use this when experiencing errors or to proactively verify service availability before making weather data requests. Returns current status, helpful messages, and links to official status pages.
AI agents call check_service_status to retrieve information from Weather Data MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only query of service status information. It has no ability to modify data, execute commands, delete resources, or affect financial systems. The blast radius of misuse is minimal—an AI agent checking service status cannot cause harm beyond potentially making unnecessary status requests. This fits the 'Read' category as it retrieves data without side effects.
From the tool's definition The tool 'check_service_status' retrieves and queries the operational status of external APIs. The description states it 'Returns current status, helpful messages, and links to official status pages'—purely informational retrieval with no side effects, data…
Attacks that exploit this kind of access
Check the operational status of the NOAA and Open-Meteo weather APIs. Use this when experiencing errors or to proactively verify service availability before making weather data requests. Returns current status, helpful messages, and links to official status pages. It is categorised as a Read tool in the Weather Data MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Weather Data MCP Server MCP server in PolicyLayer and add a rule for check_service_status: 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 Weather Data MCP Server. Nothing to install.
check_service_status 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 check_service_status 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 check_service_status. 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.
check_service_status is provided by the Weather Data MCP Server MCP server (@dangahagan/weather-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →