Get current airport weather (METAR) by ICAO code from CPTEC/INPE
AI agents call get_cptec_airport_weather to retrieve information from Mcp Ap2 without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves publicly available weather information from a weather service. It takes an ICAO code as input and returns current meteorological data (METAR). There are no side effects, no data modification, no code execution, no deletion, and no financial implications. Misuse would have minimal blast radius — an agent could only retrieve weather data, which poses no security risk.
From the tool's definition Tool description states 'Get current airport weather (METAR) by ICAO code' — a retrieval operation with no modification or side effects. The verb 'Get' and the read-only nature of querying meteorological data confirm this is a Read operation.
Documented attack patterns abuse exactly the kind of access get_cptec_airport_weather gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Ap2, and nothing reaches the server without passing your rules. This is the rule we recommend for get_cptec_airport_weather:
{
"version": "1",
"default": "deny",
"tools": {
"get_cptec_airport_weather": {}
}
} get_cptec_airport_weather is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get current airport weather (METAR) by ICAO code from CPTEC/INPE. It is categorised as a Read tool in the Mcp Ap2 MCP Server, which means it retrieves data without modifying state.
Register the Mcp Ap2 MCP server in PolicyLayer and add a rule for get_cptec_airport_weather: 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 Mcp Ap2. Nothing to install.
get_cptec_airport_weather 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_cptec_airport_weather 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_cptec_airport_weather. 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_cptec_airport_weather is provided by the Mcp Ap2 MCP server (@codespar/mcp-ap2). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Mcp Ap2, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
1300 Mcp Ap2 tools catalogued and risk-classified — across an index of 43,000+ MCP servers.