get_weather_alert_detail
AI agents call get_weather_alert_detail to retrieve information from BMKG MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves detailed information about weather alerts from Indonesia's BMKG (meteorological agency) database. It performs a data query operation with no side effects, state changes, or resource-affecting operations. The empty description reduces confidence slightly, but the naming pattern and sibling tools confirm a read-only data retrieval classification.
From the tool's definition Tool name 'get_weather_alert_detail' indicates retrieval of alert details; sibling tools like 'get_weather_alerts', 'get_weather_forecast', 'search_location_code', 'search_weather_alerts_by_kecamatan' are all read-only queries of BMKG meteorological data.
Attacks that exploit this kind of access
get_weather_alert_detail. It is categorised as a Read tool in the BMKG MCP Server MCP Server, which means it retrieves data without modifying state.
Register the BMKG MCP Server MCP server in PolicyLayer and add a rule for get_weather_alert_detail: 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 BMKG MCP Server. Nothing to install.
get_weather_alert_detail 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 get_weather_alert_detail 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 get_weather_alert_detail. 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.
get_weather_alert_detail is provided by the BMKG MCP Server MCP server (revomkg/mcp-bmkg). 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 →