Get historical drought conditions over time from the US Drought Monitor. Returns weekly drought severity percentages for the specified area and date range. The Drought Monitor is updated every Tuesday, so data points are weekly. Args: state: Two-letter US state abbreviation (e.g. 'CA', 'TX'). cou...
Risk signalsBulk/mass operation — affects multiple targets
Part of the US Drought Monitor server.
Free to start. No card required.
AI agents call get_drought_history to retrieve information from US Drought Monitor without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though get_drought_history only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"get_drought_history": {}
}
}See the full US Drought Monitor policy for all 3 tools.
These attack patterns abuse exactly the kind of access get_drought_history gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
Get historical drought conditions over time from the US Drought Monitor. Returns weekly drought severity percentages for the specified area and date range. The Drought Monitor is updated every Tuesday, so data points are weekly. Args: state: Two-letter US state abbreviation (e.g. 'CA', 'TX'). county_fips: Five-digit county FIPS code (e.g. '06037' for Los Angeles County). start_date: Start date in YYYY-MM-DD format. Defaults to one year ago. end_date: End date in YYYY-MM-DD format. Defaults to today.. It is categorised as a Read tool in the US Drought Monitor MCP Server, which means it retrieves data without modifying state.
Register the US Drought Monitor MCP server in PolicyLayer and add a rule for get_drought_history: 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 US Drought Monitor. Nothing to install.
get_drought_history 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_drought_history 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_drought_history. 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_drought_history is provided by the US Drought Monitor MCP server (https://mcp.olyport.com/drought/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 3 US Drought Monitor tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.