Get a summary of Pest Sentinel's current data coverage — how many zones, states, countries, pest types, and weeks of history are available. Use this tool to understand what's available before making other queries. Returns current platform stats. Args: - response_format ('markdown' | 'json'): ...
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_coverage 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_coverage 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_coverage:
rules:
- action: allowSee the full Pest Sentinel — AI Pest Risk Intelligence policy for all 9 tools.
Agents calling read-class tools like pestsentinel_get_coverage 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 summary of Pest Sentinel's current data coverage — how many zones, states, countries, pest types, and weeks of history are available. Use this tool to understand what's available before making other queries. Returns current platform stats. Args: - response_format ('markdown' | 'json'): Output format (default: 'markdown') Returns: Coverage stats: zone count, state/province breakdown, latest week scored, total risk scores.. 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_coverage. 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_coverage 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_coverage 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_coverage. 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_coverage 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