Low Risk

weather_current

Get current weather for a location.

How to control weather_current ↓

What weather_current does on Weather

AI agents call weather_current to retrieve information from Weather without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why weather_current needs a policy

This tool retrieves weather data for a specified location without modifying any state, executing code, or performing destructive operations. It is a straightforward data query with no side effects, making it a Read category tool with low severity risk.

From the tool's definition Tool name 'weather_current' and description 'Get current weather for a location' indicate a retrieval operation. The verb 'get' and absence of any modification, deletion, or execution keywords confirm this is a read-only query.

Documented attack patterns abuse exactly the kind of access weather_current gives an agent:

How to control weather_current

PolicyLayer is an MCP gateway — it sits between your AI agents and Weather, and nothing reaches the server without passing your rules. This is the rule we recommend for weather_current:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "weather_current": {}
  }
}

weather_current is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Weather — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about weather_current

What does the weather_current tool do? +

Get current weather for a location. It is categorised as a Read tool in the Weather MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on weather_current? +

Register the Weather 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 Weather. Nothing to install.

What risk level is weather_current? +

weather_current is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit weather_current? +

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.

How do I block weather_current completely? +

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.

What MCP server provides weather_current? +

weather_current is provided by the Weather MCP server (sjanax01/weather-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Weather tool call.

Start from Weather, 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.

9 Weather tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.