Low Risk

human_weather_tool

人間が現在地の天気を確認して報告します。

How to control human_weather_tool ↓

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

Low Risk

The tool merely queries and returns weather information observed by a human. It performs no writes, executions, destructive operations, or financial transactions. It is a straightforward information retrieval task with minimal security risk.

From the tool's definition Tool description indicates the human checks current weather at their location and reports it. This is a read-only operation that retrieves information with no side effects or modifications.

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

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

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

human_weather_tool 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 Human — 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.

Go deeper

What does the human_weather_tool tool do? +

人間が現在地の天気を確認して報告します。. It is categorised as a Read tool in the Human MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on human_weather_tool? +

Register the Human MCP server in PolicyLayer and add a rule for human_weather_tool: 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 Human. Nothing to install.

What risk level is human_weather_tool? +

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

Can I rate-limit human_weather_tool? +

Yes. Add a rate_limit block to the human_weather_tool 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 human_weather_tool completely? +

Set action: deny in the PolicyLayer policy for human_weather_tool. 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 human_weather_tool? +

human_weather_tool is provided by the Human MCP server (upamune/human-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Human tool call.

Deterministic rules across all 7 Human tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

7 Human tools catalogued and risk-classified — across an index of 42,500+ 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.