Check if the weather API is running and healthy
AI agents call check_api_health to retrieve information from Weather Info 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 to determine the operational status of the weather API. It retrieves state information (health status) with no side effects, data modifications, or ability to execute commands or trigger financial transactions. The low severity reflects minimal blast radius if misused by an AI agent.
From the tool's definition Tool name 'check_api_health' and description 'Check if the weather API is running and healthy' indicate a status check operation that retrieves health information without modifying any data or triggering external operations.
Attacks that exploit this kind of access
Check if the weather API is running and healthy. It is categorised as a Read tool in the Weather Info MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Weather Info MCP Server MCP server in PolicyLayer and add a rule for check_api_health: 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 Info MCP Server. Nothing to install.
check_api_health 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_api_health 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_api_health. 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_api_health is provided by the Weather Info MCP Server MCP server (raffay0177/mcp-server-using-fast-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 →