BROWSING / DISCOVERY search — cities, neighbourhoods, or mixed venues near a location. Supports population filtering (
AI agents call explore to retrieve information from ThinAir Geo without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries geographic and venue data to help discover places near a location. It retrieves information without creating, modifying, deleting, or executing operations. The capability to filter by population does not change its read-only nature. No irreversible actions, code execution, or financial transactions are involved.
From the tool's definition Tool description states 'BROWSING / DISCOVERY search' for 'cities, neighbourhoods, or mixed venues near a location'. The verb 'search' combined with 'browsing' and 'discovery' indicates data retrieval with no modification or side effects.
Attacks that exploit this kind of access
BROWSING / DISCOVERY search — cities, neighbourhoods, or mixed venues near a location. Supports population filtering (. It is categorised as a Read tool in the ThinAir Geo MCP Server, which means it retrieves data without modifying state.
Register the ThinAir Geo MCP server in PolicyLayer and add a rule for explore: 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 ThinAir Geo. Nothing to install.
explore 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 explore 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 explore. 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.
explore is provided by the ThinAir Geo MCP server (thinairtelematics/thinair-geo). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
explore is one line of ThinAir Geo's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →