AI agents call get_fact_ranking 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.
This tool appears to be a query/retrieval function that fetches ranked factual data without side effects. No description was provided, which slightly lowers confidence, but the naming convention and context of weather data retrieval operations strongly indicates it is a Read operation. Even if misused by an AI agent, retrieving ranked weather station facts poses minimal security risk.
From the tool's definition Tool name 'get_fact_ranking' follows the 'get_*' pattern consistent with sibling tools like 'get_all_stations', 'get_forecast_for_cell', and 'get_latest_observation', all of which are retrieval operations.
Documented attack patterns abuse exactly the kind of access get_fact_ranking 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_fact_ranking:
{
"version": "1",
"default": "deny",
"tools": {
"get_fact_ranking": {}
}
}get_fact_ranking 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_fact_ranking. 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_fact_ranking: 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_fact_ranking 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_fact_ranking 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_fact_ranking. 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_fact_ranking 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.