weather_current
Get current weather conditions for any location worldwide. Returns temperature, feels-like, humidity, wind speed and direction, cloud cover, pressure, precipitation, UV index, and visibility. Use this for 'what's the weather?', 'is it raining in Houston?', 'how hot is it outside?', 'what's the te...
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/weather-current.md
What weather_current does on Livedatalink
AI agents call weather_current to retrieve information from Livedatalink 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 |
|---|---|---|---|
location | string | Yes | City, zip code, or place name (e.g., 'Houston, TX', '77001', 'Paris') |
Parameters from the server's own tool schema.
Why weather_current is rated Low
This tool queries a weather data source and returns meteorological information without side effects. It does not create, modify, delete, execute code, or commit financial obligations. The worst-case misuse scenario—an AI agent requesting weather for many locations—would have negligible impact. Classified as Read with low severity.
From the tool's definition Tool retrieves current weather conditions and returns data (temperature, humidity, wind speed, cloud cover, pressure, precipitation, UV index, visibility) with no modification of external systems.
Attacks that exploit this kind of access
The rule that runs weather_current safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Livedatalink, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For weather_current, this is the rule to start with:
weather_current 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 Livedatalink, apply this rule, and every weather_current call is checked against it from then on.
Questions about weather_current
Get current weather conditions for any location worldwide. Returns temperature, feels-like, humidity, wind speed and direction, cloud cover, pressure, precipitation, UV index, and visibility. Use this for 'what's the weather?', 'is it raining in Houston?', 'how hot is it outside?', 'what's the temperature in New York?', 'do I need a jacket?', or any current weather question. Works for any city, zip code, or place name globally. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
weather_current accepts 1 parameter: location. Required: location. The full parameter table on this page comes from the server's own tool schema.
Register the Livedatalink MCP server in PolicyLayer and add a rule for weather_current: 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 Livedatalink. Nothing to install.
weather_current 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 weather_current 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 weather_current. 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.
weather_current is provided by the Livedatalink MCP server (https://livedatalink.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Livedatalink, and thousands of servers like it.
This server
Across the catalogue