AI agents call get_historical_observations to retrieve information from WeatherXM Pro MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name and naming pattern strongly suggest retrieval of historical weather observation data. Consistent with sibling tools that fetch, query, or retrieve information without modifying state. No evidence of write, execute, delete, or financial operations. Low severity because querying historical data has minimal blast radius.
From the tool's definition Tool name 'get_historical_observations' indicates data retrieval. All sibling tools on this server are read-only queries (get_*, search_*), and the tool description is empty, preventing any evidence of side effects or destructive actions.
Documented attack patterns abuse exactly the kind of access get_historical_observations gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and WeatherXM Pro MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_historical_observations:
{
"version": "1",
"default": "deny",
"tools": {
"get_historical_observations": {}
}
}get_historical_observations is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
get_historical_observations. It is categorised as a Read tool in the WeatherXM Pro MCP Server MCP Server, which means it retrieves data without modifying state.
Register the WeatherXM Pro MCP Server MCP server in PolicyLayer and add a rule for get_historical_observations: 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 WeatherXM Pro MCP Server. Nothing to install.
get_historical_observations 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_historical_observations 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_historical_observations. 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_historical_observations is provided by the WeatherXM Pro MCP Server MCP server (weatherxm/weatherxm-pro-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from WeatherXM Pro MCP Server, 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.
11 WeatherXM Pro MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.