Get historical weekly risk scores for a zone to see how pest pressure has changed over time. Returns scores week-by-week going back up to 12 weeks. Useful for identifying seasonal patterns, long-term trends, or evaluating territory before expansion. Args: - zone_id (string): The UUID of the zone ...
Part of the Pest Sentinel — AI Pest Risk Intelligence server.
Free to start. No card required.
AI agents call pestsentinel_get_zone_history to retrieve information from Pest Sentinel — AI Pest Risk Intelligence 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 pestsentinel_get_zone_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": {
"pestsentinel_get_zone_history": {}
}
}See the full Pest Sentinel — AI Pest Risk Intelligence policy for all 9 tools.
These attack patterns abuse exactly the kind of access pestsentinel_get_zone_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 weekly risk scores for a zone to see how pest pressure has changed over time. Returns scores week-by-week going back up to 12 weeks. Useful for identifying seasonal patterns, long-term trends, or evaluating territory before expansion. Args: - zone_id (string): The UUID of the zone - pest_type (string, optional): Filter to a single pest type - weeks (number): Number of weeks of history to return, 1–12 (default: 6) - response_format ('markdown' | 'json'): Output format (default: 'markdown') Returns: Weekly scores with trend and confidence for the requested period. Examples: - "How has mosquito pressure changed in Tampa over the last 6 weeks?" → zone_id + pest_type='mosquitoes' - "Show termite history for Houston zone" → zone_id + pest_type='termites'. It is categorised as a Read tool in the Pest Sentinel — AI Pest Risk Intelligence MCP Server, which means it retrieves data without modifying state.
Register the Pest Sentinel — AI Pest Risk Intelligence MCP server in PolicyLayer and add a rule for pestsentinel_get_zone_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 Pest Sentinel — AI Pest Risk Intelligence. Nothing to install.
pestsentinel_get_zone_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 pestsentinel_get_zone_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 pestsentinel_get_zone_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.
pestsentinel_get_zone_history is provided by the Pest Sentinel — AI Pest Risk Intelligence MCP server (pestsentinel/pest-intelligence). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 9 Pest Sentinel — AI Pest Risk Intelligence 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.