Search for zones by name or city to find the zone ID needed for risk score queries. Use this tool when you know a city or neighborhood name and need to find the matching zone ID before calling pestsentinel_get_zone_scores or pestsentinel_get_zone_history. Args: - query (string): City, neighborhoo...
Risk signalsAccepts freeform code/query input (query)
Part of the Pest Sentinel — AI Pest Risk Intelligence server.
Free to start. No card required.
AI agents call pestsentinel_search_zones 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_search_zones 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_search_zones": {}
}
}See the full Pest Sentinel — AI Pest Risk Intelligence policy for all 9 tools.
These attack patterns abuse exactly the kind of access pestsentinel_search_zones 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.
Search for zones by name or city to find the zone ID needed for risk score queries. Use this tool when you know a city or neighborhood name and need to find the matching zone ID before calling pestsentinel_get_zone_scores or pestsentinel_get_zone_history. Args: - query (string): City, neighborhood, or zone name to search (min 2 characters) - response_format ('markdown' | 'json'): Output format (default: 'markdown') Returns: Matching zones with their IDs, regions, and locations. Examples: - "Find zones in Nashville" → query='Nashville' - "Search for Brooklyn zones" → query='Brooklyn' - "Is Columbus covered?" → query='Columbus'. 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_search_zones: 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_search_zones 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_search_zones 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_search_zones. 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_search_zones 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.