AI agents call get_3_days_weather to retrieve information from Roc Cwa without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves weather forecast data for a 3-day period from a public meteorological service. It is a read-only query operation with no side effects, data modification, code execution, or financial implications. The only minor uncertainty is the empty tool description, but the naming convention and server context make its purpose clear.
From the tool's definition Tool name 'get_3_days_weather' and server description indicating it 'access[es] Taiwan Central Weather Administration data, including 3-day...weather forecasts'; the sibling tool 'get_1_week_weather' and 'get_historical_rainfall' all appear to be retrieval…
Attacks that exploit this kind of access
get_3_days_weather. It is categorised as a Read tool in the Roc Cwa MCP Server, which means it retrieves data without modifying state.
Register the Roc Cwa MCP server in PolicyLayer and add a rule for get_3_days_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 Roc Cwa. Nothing to install.
get_3_days_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_3_days_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_3_days_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_3_days_weather is provided by the Roc Cwa MCP server (lwsinclair/roc-cwa-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →