Get a high-level pest risk summary for an entire state, province, or city — aggregated across all zones in that region. Returns average and peak scores per pest type, with rising/falling/stable zone counts. Ideal for market analysis, territory planning, and understanding which pests are dominant...
Bulk/mass operation — affects multiple targets
Part of the Pest Sentinel — AI Pest Risk Intelligence MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents call pestsentinel_get_regional_summary 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_regional_summary 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.
tools:
pestsentinel_get_regional_summary:
rules:
- action: allowSee the full Pest Sentinel — AI Pest Risk Intelligence policy for all 9 tools.
Agents calling read-class tools like pestsentinel_get_regional_summary have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.
Get a high-level pest risk summary for an entire state, province, or city — aggregated across all zones in that region. Returns average and peak scores per pest type, with rising/falling/stable zone counts. Ideal for market analysis, territory planning, and understanding which pests are dominant in a region. Args: - province (string, optional): State/province code e.g. 'TX', 'FL', 'ON' - region (string, optional): City/region name e.g. 'Chicago', 'Miami', 'Toronto' - country (string, optional): 'US' or 'CA' - response_format ('markdown' | 'json'): Output format (default: 'markdown') Returns: Per-pest aggregated stats: avg score, peak score, zone count, rising/falling breakdown. Examples: - "What's the pest outlook for Florida this week?" → province='FL' - "Summarize pest risk in Chicago" → region='Chicago' - "Compare pest types across all US zones" → country='US'. 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.
Add a rule in your Intercept YAML policy under the tools section for pestsentinel_get_regional_summary. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Pest Sentinel — AI Pest Risk Intelligence MCP server.
pestsentinel_get_regional_summary 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_regional_summary rule in your Intercept 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 Intercept policy for pestsentinel_get_regional_summary. 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_regional_summary is provided by the Pest Sentinel — AI Pest Risk Intelligence MCP server (pestsentinel/pest-intelligence). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept