decode_metar_taf
skypeek: Decode a METAR or TAF weather report. To fetch the latest report use get_metar. Returns one METAR or TAF report you paste, decoded into wind, visibility, weather, clouds, temperature and dew point, altimeter and the flight category (VFR / MVFR / IFR / LIFR) (TAF: each forecast period and...
This record as markdown: /tools/dev-tanod-tanod/decode-metar-taf.md
What decode_metar_taf does on Tanod
AI agents call decode_metar_taf to retrieve information from Tanod 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 |
|---|---|---|---|
raw | string | Yes | One METAR or TAF report as text (at most 2,000 characters). |
kind | string | — | Report type; auto detects it. |
Parameters from the server's own tool schema.
Why decode_metar_taf is rated Low
Even though decode_metar_taf only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs decode_metar_taf safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Tanod, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For decode_metar_taf, this is the rule to start with:
decode_metar_taf 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 Tanod, apply this rule, and every decode_metar_taf call is checked against it from then on.
Questions about decode_metar_taf
skypeek: Decode a METAR or TAF weather report. To fetch the latest report use get_metar. Returns one METAR or TAF report you paste, decoded into wind, visibility, weather, clouds, temperature and dew point, altimeter and the flight category (VFR / MVFR / IFR / LIFR) (TAF: each forecast period and the temperature extremes); groups it does not recognise are listed in unparsed. Informational only: not for flight planning or navigation. Decoded locally (no upstream call). Day and hour are as reported (UTC); a METAR or TAF carries no month or year. A report it cannot read is a 422 invalid_report (not charged). Typically under 0.1 s. Price: USD 0.001. Free: 5 skypeek calls per IP per UTC day. Docs: https://tanod.dev/learn/decode-metar-taf-api.html. It is categorised as a Read tool in the Tanod MCP Server, which means it retrieves data without modifying state.
decode_metar_taf accepts 2 parameters: raw, kind. Required: raw. The full parameter table on this page comes from the server's own tool schema.
Register the Tanod MCP server in PolicyLayer and add a rule for decode_metar_taf: 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 Tanod. Nothing to install.
decode_metar_taf 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 decode_metar_taf 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 decode_metar_taf. 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.
decode_metar_taf is provided by the Tanod MCP server (https://tanod.dev/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Tanod, and thousands of servers like it.
This server
Across the catalogue